Framework overlap

Does FFIEC Cybersecurity Assessment Tool (CAT) cover NATO AQAP 2110?

You hold FFIEC Cybersecurity Assessment Tool (CAT) and have been told to do NATO AQAP 2110. Here is how much overlaps, control by control.

100% of NATO AQAP 2110 you already have

FFIEC Cybersecurity Assessment Tool (CAT) already covers about 100% of NATO AQAP 2110, leaving 0 of 8 controls as genuinely new work.

Already covered 0 Likely covered 8 New work 0

No control in FFIEC Cybersecurity Assessment Tool (CAT) maps directly to one in NATO AQAP 2110. Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in FFIEC Cybersecurity Assessment Tool (CAT) reaches these. This is the list to scope.

Nothing. Every control is reached.

Show the 8 you already have
AQAP2110-1
Quality Management System Aligned to ISO 9001 plus NATO Supplementary Requirements
AQAP2110-2
Government Quality Assurance Representative (GQAR) Authority and Access
AQAP2110-3
Design and Development Control - NATO plus ISO 13485 Cross-Walk
AQAP2110-4
Configuration Management and Change Control
AQAP2110-5
Risk and Opportunity Management
AQAP2110-6
Subcontractor Supply Chain Control plus Counterfeit Material Prevention
AQAP2110-7
Production, Special Processes, Inspection, Testing, and Records
AQAP2110-8
Internal Audit, Management Review, Corrective Action, CofC, and Continual Improvement

How this is calculated

Already covered means a mapping runs from a control in FFIEC Cybersecurity Assessment Tool (CAT) 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