Gsecraif addresses two aspects of security; protecting against data loss and guarding against unauthorised access. Obviously gsecraif is not a panacea for all your security issues, but it may be able to help within it's areas of envisaged use such as transferring data or storing data on external systems such as cloud services.
No original data in component files
When gsecraif is used to split a file in to component files, none of the component files contain any data from the original file. A non technical explanation is provided here.
When gsecraif splits a file it reads a number of bytes at a time, the number of bytes read is one less than the number of component files the original file is to be split in to. This is to allow for a special (parity) byte be stored so that the original file can be recovered if one of the components is lost.
Having read in a number of bytes (and calculated the special byte), gsecraif distributes those bytes among the component files, but before doing so carries out some further processing. Each of the bytes consists of eight bits and gsecraif takes all the bits and either "spins them around" (rotates them) or mixes them in some other way. All the original bits are in the resulting bytes, but each byte now contains bits from two (or more) of the original bytes. Thus none of the bytes in the component files match any of the bytes in the original file.
The utility gsecraif, does not use encryption. Under some circumstances there may be restrictions on the use of encryption. The history of encryption seems to be a cycle of development of and breaking of new cyphers. Of course gsecraif can be used in conjunction with encryption (where permitted) and this is described in the security document.
The security aspects of gsecraif are described in the security document.