• jt

How Do You Assess the Quality of Your Security Risk Management?

One element that is often missing or inadequate is how to ensure, and to assess the effectiveness of security risk management and security assessments.


Indicators


The following are examples of some indicators which should be evident in a security risk assessment or management system.

  • Accountability-risk acceptance. The individual who accepted the risk is clearly identified.

  • Accountability-risk treatment. The individual who is responsible for treating the risk is clearly identified.

  • Existing controls. Explicitly identified and linked to risks.

  • Scope, Context, and Criteria are clearly identified.

  • Consequences and likelihood are assessed and supporting evidence is referenced.

  • Methodology of risk and threat assessments are documented, use (or adapt) a robust and recognized framework or methodology.

  • Threat and risk assessments follow and comply with the identified methodology. Eg: SRMBOK Methodology, ISO31000 RiskManagement Standard

  • Human Factors are considered and documented.

  • Risk assessment tools are correctly applied and minimize biases or subjectivity as much as possible.

  • Risk assessment tools are appropriate for the scale of the activity.

  • Risk statements meet the criteria outlined in ‘RiskStatements’.


Writing a Risk Statement

  • Risk Treatments are explicitly linked to risks and address root cause(s).


Guidance For Assessment Of SRM/A Quality Indicators

The following 10-point scoring method is designed to provide guidance when assessing the quality of security risk assessments and management systems.

  1. No intention to implement the requirements of the indicator.

  2. Some awareness and intention to implement. May be limited or inadequate action to implement at this stage.

  3. Early progress toward implementation. Evidence of management commitment of resources to the requirements of the indicator.

  4. Preparation for consistent implementation is well under way. Early drafts of documents supporting the indicator may be available.

  5. Basic requirements of the indicator are almost in place. Documents may be in draft form. Planning may have occurred but plans are not fully implemented. Implementation of the basic requirements of the indicator is imminent.

  6. Satisfies minimum requirements of the indicator. Basic documentation can be produced if specified in the indicator. System may be relatively new but there is evidence that requirements are applied within the organisation. Compliance with minimum standards and/or relevant legislation.

  7. Basic documentation supports the requirements of the indicator even though it may not be specified in the indicator itself. Continuous improvement processes developing and regularly demonstrated in documentary form. Monitoring procedures in place aspart of continuous improvement.

  8. Requirements of the indicator have been in place long enough to allow evaluation and review. Maintaining more than the minimum requirements, but room for improvement. Strong supporting documentation. Ongoing continuous improvement.

  9. Sustained performance in parts of the organisation where the requirements of the indicator apply. Some minor problems may occur from time to time but these are rare. Continuous Improvement is clearly evident.

  10. Continuous Improvement processes ensure sustained performance. Could be used as a benchmark. Excellent supporting documentation that is updated as part of continuous improvement. Consistent application of the requirements of the indicator overtime. Based on current industry practices, the assessors cannot identify scope for improvement

24 views0 comments

Recent Posts

See All

Other Security Frameworks

Security Frameworks The following is a partial list of sources for security-related frameworks. Their presence here is not an endorsement, just a resource if you are looking for more references. I hav

©2019 by Julian Talbot