Framework overlap

Does ISO 14001:2015 cover ISO 27005:2022?

You hold ISO 14001:2015 and have been told to do ISO 27005:2022. Here is how much overlaps, control by control.

36% of ISO 27005:2022 you already have

ISO 14001:2015 already covers about 36% of ISO 27005:2022, leaving 25 of 39 controls as genuinely new work.

Already covered 7 Likely covered 7 New work 25

What is genuinely new work

Nothing in ISO 14001:2015 reaches these. This is the list to scope.

10.5.2
Monitoring and reviewing factors influencing risks
10.7
Corrective action
3.1
Terms related to information security risk
3.2
Terms related to information security risk management
5.1
Information security risk management process
5.2
Information security risk management cycles
6.1
Organizational considerations
6.2
Identifying basic requirements of interested parties
6.3
Applying risk assessment
6.4
Establishing and maintaining information security risk criteria
6.4.2
Risk acceptance criteria
6.4.3
Criteria for performing information security risk assessments
7.2
Identifying information security risks
7.2.2
Identifying risk owners
7.4
Evaluating the information security risks
7.4.1
Comparing the results of risk analysis with the risk criteria
7.4.2
Prioritizing the analysed risks for risk treatment
8.2
Selecting appropriate information security risk treatment options
8.5
Producing a Statement of Applicability
8.6
Information security risk treatment plan
8.6.1
Formulation of the risk treatment plan
8.6.2
Approval by risk owners
8.6.3
Acceptance of the residual information security risks
9.1
Performing information security risk assessment process
9.2
Performing information security risk treatment process
Show the 14 you already have
10.2
Leadership and commitment
10.3
Communication and consultation
10.4
Documented information
10.4.2
Documented information about processes
10.4.3
Documented information about results
10.6
Management review
10.8
Continual improvement
10.1
Context of the organization
10.5
Monitoring and review
6.5
Choosing an appropriate method
7.3
Analysing information security risks
7.3.2
Assessing potential consequences
7.3.3
Assessing likelihood
7.3.4
Determining the levels of risk

How this is calculated

Already covered means a mapping runs from a control in ISO 14001:2015 to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition