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

Add a best practice description on logging security events #3

Open
ereshetova opened this issue Mar 25, 2019 · 1 comment
Open

Add a best practice description on logging security events #3

ereshetova opened this issue Mar 25, 2019 · 1 comment

Comments

@ereshetova
Copy link
Contributor

If a WoT Servient enforces security authentication & authorization on its provided web interfaces, it is a good practice to log these events (especially unsuccessful, i.e rejects) since they latter can be analyzed if security audit is performed.

@mmccool
Copy link
Contributor

mmccool commented Dec 13, 2021

Any other best practices we could recommend? Some possibilities:

  • IP Jail (block IPs that try too many times to guess a password)
  • Firewalls so devices can only do what they are supposed to be doing (related to MUDs), including outgoing connections
  • Isolated networks; small security domains
  • Rate-limiting connection attempts
  • Frequent security audits
  • Password rotation (and always change default passwords)
  • Integrity checks

One question is: are these appropriate, or should we be referring to another document?
Not to suggest that THIS issue won't be resolved after just adding logging, but if any of the above make sense we can add issues for them.

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

No branches or pull requests

2 participants