You can investigate escalated privileges by collecting relevant machine data from your endpoint. You can use the machine data to create your own analysis. Before you start your investigation you will need to determine normal activity on your endpoint. Normal activity is the scope of functionality of the software on your endpoint during periods of low activity and high activity.
You will need some kind of software that periodically collects specific machine data from your endpoint like my software developed in Python that's available for free download at https://github.com/davidbrennerjr/server-stats-collector
Ingest one or more of the following machine data from Category #1. Ingest one or more of the following machine data from Category #2.
Category #1
- General system-wide error messages from /var/log/syslog
- Auditing logs of application rulesets
- Auditing logs of security contexts
- Auditing logs of login attempts from /var/log/auth.log
- Auditing logs of user management or group management
- Auditing logs of password management
- Application specific logs from /var/log
- File system status of files and directories from stat
- Auditing logs of package management
- Auditing logs of configuration management
Category #2
- Raw dumps from sniffing at Layers 2-3
- Raw dumps from /proc of kernel data structures
- Raw dumps of kernel routing tables
- Network services configuration files
- Network interface configuration files
- Headless raw dumps of active executables
- Memory profiles of active executables
- Summaries of memory debugging, memory management or memory profiling
- File integrity checking with checksum matching prior to either base infection or payload infection
- Summaries of resource utilization: physical, network, I/O, disks, processes, etc.
Do you have a suggestion about how to improve this blog? Let's talk about it. Contact me at David.Brenner.Jr@Gmail.com or 720-584-5229.
Comments
Post a Comment
Comments to this blog will be reviewed within 72 hours. No trolling please