Saturday, July 6, 2024

Vulnerability Management - Scream Test

What will you do when you went through CMDB and did not find any ownership info. of a server ? You initiated a thread as well but no one is claiming/accepting ownership of the server.


You run a scream test 😁 .

It is a simple – remove it and wait for the screams test. If someone screams, put it back. The Scream Test can be applied to any product, service or capability – particularly when there is poor ownership or understanding of it’s importance.

Typically it consists of the following steps:

  1. Display the message “Hey, is this your server, contact us?” on the sign-in splash page for two weeks.
  2. Restart the server once each day for two weeks to see whether someone opens a ticket (in other words, screams).
  3. Shut down the server for two weeks and see whether someone opens a ticket. (Again, whether they scream.)
  4. Retire the server, retaining the storage for a period, just in case.

From vulnerability management standpoint, there are two benefits:
  1. If such servers/applications are removed, a lot of vulnerabilities are removed.
  2. If someone screams, well, you know the owner now 😛 .

Happy Learning
hashtagvulnerabilitymanagement hashtagcybersecurity

No comments:

Post a Comment

Vulnerability Management - Understanding vulnerability posture

Understanding the vulnerability posture of an organisation at a basic level helps you drive remediation efforts. So, I don't know what t...