Important Controls and Measures for Vulnerability and Patch Management

, , ,
When you define and implement your vulnerability and patch management process (see: How to Implement a Vulnerability and Patch Management Process) it is always best practice to think about and define possible requirements, controls and measures. These are going to help you to protect against current threats and protect your organization.

 

Here you can find a list of examples and best practices for different measures and controls in case of vulnerabilty management and patch management:

1. Vulnerability Classification measures and controls:

1.1. Matrix of Vulnerability Criticality Levels
1.2. Asset Referential List (Asset Management)
1.3. Asset Security Classification and Impact Analysis
1.4. Assets exposure to Internet or public networks

2. Vulnerability Identification and Detection measures and controls:

2.1. External and internal vulnerablity scans
2.2. Definition of vulnerability scan frequency
2.3. Automated vulnerability scans
2.4. Authenticated vulnerability scans
2.5. Freuquent updates of vulnerability scanning tools
2.6. Definition of the scope for vulnerability scans
2.7. Frequent scanning of operating system masters or golden images
2.8. Manual assessement for vulnerabilities or penetration tests

3. Vulnerability Logging, Tracing and Monitoring measaures and controls:

3.1. Vulnerability tracking repository
3.2. Tracking of the lifecycle of a vulenerability
3.3. Manually watching and security monitoring

4. Vulnerability Reporting measures and controls:

4.1. Definition of Key Risk Indicators (KRIs) and Key Performance Indicators (KPIs)

(see KPI Examples for Vulnerability and Patch Management)

4.2. Definition of reporting templates or dashboards
4.3. Tracking and reporting of failed patch or other remediation deployments

5. Patch Deployment and Remediation measures and controls

5.1. Deploying of all security patches for all operating systems or IT Assets
5.2. Updating of operating system master or golden images
5.3. Definition of the priority of vulnerability remediation
5.4. Verification of the success of a deployed patch or remediation solution (e.g. via scan or pentest)
5.5. Definition of SLAs for detecting, analyzing and patching, e.g. 10 days for critical patches

This might be also interesting:

KPI Examples for Vulnerability and Patch Management

, , , ,
If you have implemented a Vulnerability and Patch Management Process (see: How to Implement a Vulnerability and Patch Management Process) you should also define Key Performance Indicators (KPI) and Key Risk Indicators (KRI) to monitor the effectivness of your Vulnerability and Patch Management controls and measures.   1. What are KPIs and KRIs or Metrics related to Vulnerability and Patch Management? KPIs and KRIs help you to understand, measure and improve your vulnerability management process and patch management process. They…
Read More

How to Implement a Vulnerability Management Process

, , , , ,
Vulnerability and Patch Management are major and essential tasks of the Information- and IT-Security. A good vulnerability and patch management process helps you to identify, evaluate, prioritize and reduce the technical security risks of your company or organization. Even if you are not planning to implement security frameworks like ISO 27001 or NIST Cybersecurity Framework (CSF) you should consider to implement a basic vulnerability management process or technical measures and controls to be prepared for critical cybersecurity attacks or threats.…
Read More

ISO 27001 How to Define your Scope Statement

, , , ,
Defining your ISO 27001 scope statement is one of the first steps for building your ISMS. Although it is just a short separate document or small paragraph in your security policy it is one of the most important point. This is because every next step is related to your scope or area of application. In this article you can find out why the definition of your scope is so important, how to write your statement, what it does have to…
Read More

ISO 27001 Required Documents, Policies and Procedures

, , ,
Besides the question what controls you need to cover for ISO 27001 the other most important question is what documents, policies and procedures are required and have to be delivered for a successful certification. The biggest goal of ISO 27001 is to build an Information Security Management System (ISMS). That is a framework of all your documents including your policies, processes and procedures and others that I will cover here in this article. What is the problem? The biggest challenge…
Read More

ISO 27001 Controls you need to cover

, , ,
If you are about to start a project for implementing the ISO 27001 security framework you want to know which controls you need to cover. This is one of the first questions you always get as a consultant. And it is one of the most important because you want to know about the size and therefor the time and budget you need to successfully implement this security standard. Here I want to give a quick overview about the controls for…
Read More

Share this article

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.
You need to agree with the terms to proceed

Menu