Access Keys:
Skip to content (Access Key - 0)

Logging Landing Page

For more information on securing your data, see Information Protection @ MIT.

On this page:


Logs keep track of what is happening on a computer system or network and help identify who did what and when. If a system is compromised, the logs on that system can't be trusted to provide an accurate timeline of events as attackers will often try to cover their tracks.

Ensuring authentication and access activity is logged to a secondary device helps ensure information about user and system interactions in the environment is captured, stored, protected, and available for retrieval during troubleshooting and investigations.

How to Use

If you are managing or administering multiple systems, it's a good practice to set up a log server. Depending on which IS&T resources your department is utilizing, this may already be done for you.

  • If your device is on the MIT Windows domain, you do not need to set up a logging server.
  • If you are using an IS&T Managed server (Windows or Linux), you do not need to set up a logging server.

If your DLC would like to manage their own logging infrastructure, there are a few open source options:

See Also

Have Questions or Still Need Help?

IS&T Contributions

Documentation and information provided by IS&T staff members

Last Modified:

July 07, 2020

Get Help

Request help
from the Help Desk
Report a security incident
to the Security Team
infoprotect infoprotect Delete
c-logging c-logging Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
This product/service is:
Easy to use
Difficult to use

This article is:
Adaptavist Theme Builder (4.2.3) Powered by Atlassian Confluence 3.5.13, the Enterprise Wiki