Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MinSec Check: SaaS/PaaS: Logging and Auditing #27

Open
akkornel opened this issue May 6, 2018 · 1 comment
Open

MinSec Check: SaaS/PaaS: Logging and Auditing #27

akkornel opened this issue May 6, 2018 · 1 comment
Labels
content Web site content

Comments

@akkornel
Copy link
Member

akkornel commented May 6, 2018

In MinSec for SaaS/PaaS, the Logging and Auditing item has the following:

1. Enable any available application logging that would assist in a forensic investigation in the event of a compromise. Seek vendor or ISO guidance as needed.
2. Contractually ensure that the provider can export logs at the request of Stanford within five days.

For point 1, endpoints can already be made to log the transfer of individual files, with references back to a transfer ID. The Server docs can be updated to enable this logging. General transfer details are stored with Globus, and we are able to query them directly already, using their API.

The only missing logs are logs of endpoint activations, and logs of metadata activity. For metadata activity, that's going to be logged starting with Globus Connect Server 5.1. So, Medium Risk users should move to 5.1 once it's out. And for endpoint activation logs, we'll have to get that from Globus when needed.

For point 2, we'll have to check in to this. For example, if all needed logs are available on the endpoints, then it would be up to the endpoint sysadmin (someone else at Stanford) to retrieve them.

@akkornel akkornel added the content Web site content label May 6, 2018
@akkornel akkornel added this to the Initial Release milestone May 6, 2018
akkornel added a commit that referenced this issue May 6, 2018
For Medium Risk, we need TLS version 1.1 or later, and we need to
"Enable any available application logging that would assist in a
forensic investigation in the event of a compromise."  Both of these
things can be done in GridFTP configuration, so instructions are added
to enable both.

We have to put the instructions here, because
/var/lib/globus-connect-server only gets created when
globus-connect-server-setup is run.

Updates #25 and #27
@akkornel
Copy link
Member Author

Point 1 is addressed by commit 5880275.

For point 2, I have opened Globus support ticket 309614.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Web site content
Projects
None yet
Development

No branches or pull requests

1 participant