When creating a payment file, IFS currently outputs to a folder that our externals BACs program will upload and process.
We are trying to secure this by making the folder location read only so that the file cannot be manipulated between IFS and BACs program. However, when trying to create the file in IFS we now encounter an error because of the read only status of folder.
Is there a way that IFs can send a file to a read only folder that we cannot manipulate?
The folder can’t be read-only AND still be open to allow IFS to write to it. You should be able to set the permissions on the folder itself though that make it clear that individuals outside the IFS system connection do not have access to the folder to modify the files. You would give them read-only access.
This should still be an auditable trail that reliably shows the files transferred can’t be changed on that folder.
The folder can’t be read-only AND still be open to allow IFS to write to it. You should be able to set the permissions on the folder itself though that make it clear that individuals outside the IFS system connection do not have access to the folder to modify the files. You would give them read-only access.
This should still be an auditable trail that reliably shows the files transferred can’t be changed on that folder.
Any links or tips on how to make the folder secure that only files that are created in IFS can be saved there and no-one has external access to amend?
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
