Central Logging: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
** The logs are sent to the central logging server managed by the university. Where they are imported into Splunk and are only viewable to the people with access to the cs logging domain. | ** The logs are sent to the central logging server managed by the university. Where they are imported into Splunk and are only viewable to the people with access to the cs logging domain. | ||
* '''Why is it Logged?''' | * '''Why is it Logged?''' | ||
** This is to cover a Security Policy issued for High and Moderate risk machines (and may eventually be required for Low risk machines). The policy for this can be viewed [https://it.vt.edu/content/dam/it_vt_edu/policies/Standard_for_Information_Technology_Logging.pdf here.] | ** This is to cover a Security Policy issued for High and Moderate risk machines (and may eventually be required for Low risk machines). The Virginia Tech policy for this can be viewed [https://it.vt.edu/content/dam/it_vt_edu/policies/Standard_for_Information_Technology_Logging.pdf here.] | ||
Revision as of 08:36, 19 August 2024
Questions about Logging
- What is Logged?
- For Windows: The Windows events logs: Application, System, Security, ForwardedEvents, Microsoft-Windows-Powershell, and WindowsPowerShell
- For Mac: Mac ASL logs (excluding debug and traces).
- Where is it Logged?
- The logs are sent to the central logging server managed by the university. Where they are imported into Splunk and are only viewable to the people with access to the cs logging domain.
- Why is it Logged?
- This is to cover a Security Policy issued for High and Moderate risk machines (and may eventually be required for Low risk machines). The Virginia Tech policy for this can be viewed here.