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.

Sign up for GitHub

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

Jump to bottom

xnumon self-defense #18

Open
droe opened this issue Jun 17, 2018 · 0 comments
Open

xnumon self-defense #18

droe opened this issue Jun 17, 2018 · 0 comments
Labels
pri:low not a priority but contribution welcome type:feature request for additional functionality

Comments

@droe
Copy link
Owner

droe commented Jun 17, 2018 •
edited
Loading

Config changes are already monitorable by watching eventcode 0 for unexpected settings and agent restarts. However, self-defense could be further improved, perhaps by:

  • Including hashes of configuration file in eventcode 0 events
  • Logging writes to configuration, binary, control utility, log files

Having said that, an attacker with escalated privileges will always be able to disrupt or disable xnumon.
@droe droe added the type:feature request for additional functionality label Jun 17, 2018
@droe droe added type:maturity code maturity and technical debt pri:low not a priority but contribution welcome labels Jul 24, 2018
@droe droe removed the type:maturity code maturity and technical debt label Aug 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pri:low not a priority but contribution welcome type:feature request for additional functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@droe