21% of BRCGS Global Standard for Food Safety Issue 9 you already have
ISO 9001:2015 already covers about 21% of BRCGS Global Standard for Food Safety Issue 9, leaving
31 of 39 controls as genuinely new work.
Already covered 0
Likely covered 8
New work 31
No control in ISO 9001:2015
maps directly to one in BRCGS Global Standard for Food Safety Issue 9. 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 ISO 9001:2015 reaches these. This is the list to scope.
2.1Internal Data Flow Security
2.4Utilize Automated Software Inventory Tools
3.2Establish and Maintain a Data Inventory
3.4Enforce Data Retention
4.5Implement and Manage a Firewall on End-User Devices
4.6Securely Manage Enterprise Assets and Software
5.4Establishing Audit Programme
BRCGS-1.1Senior Management Commitment
BRCGS-1.2Food Safety Culture Plan
BRCGS-2.1HACCP Team and Prerequisite Programmes
BRCGS-2.3Critical Control Points
BRCGS-3.1Food Safety and Quality Manual
BRCGS-3.11Product Recall and Withdrawal
BRCGS-3.5Supplier Approval and Performance Monitoring
BRCGS-4.1Site Standards and Layout
BRCGS-4.10Foreign Body Detection
BRCGS-4.11Housekeeping and Hygiene
BRCGS-4.13Pest Management
BRCGS-4.3Security and Food Defence
BRCGS-4.9Chemical and Physical Product Contamination Control
BRCGS-5.1Product Design and Development
BRCGS-5.3Allergen Management
BRCGS-5.4Product Authenticity and Claims
BRCGS-5.5Product Packaging
BRCGS-6.1Control of Operations
BRCGS-6.3Calibration and Control of Measuring Devices
BRCGS-7.2Personal Hygiene
Show the 8 you already have
1.1SWIFT Environment Protection
1.2Operating System Privileged Account Control
1.3Virtualisation Platform Protection
3.3Configure Data Access Control Lists
3.5Securely Dispose of Data
How this is calculated
Already covered means a mapping runs from a control in ISO 9001: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