63% of Nevada Gaming Control Board Cybersecurity Requirements you already have
AS9100D already covers about 63% of Nevada Gaming Control Board Cybersecurity Requirements, leaving
3 of 8 controls as genuinely new work.
Already covered 0
Likely covered 5
New work 3
No control in AS9100D
maps directly to one in Nevada Gaming Control Board Cybersecurity Requirements. 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 AS9100D reaches these. This is the list to scope.
NGCB-2Cybersecurity Best Practices Framework Adoption
NGCB-3Risk Assessment, Risk Management, and Ongoing Risk Monitoring
NGCB-4Designated Cybersecurity Officer and Personnel Training
Show the 5 you already have
NGCB-1Regulation 5.260 Scope, Applicability, and Licensee Categories
NGCB-5Technical Security Controls - Access + Network + Encryption + Vulnerability + Logging
NGCB-6Incident Response, 72-Hour NGCB Notification, and Independent Investigation
NGCB-7Patron and Employee Data Protection + Data Inventory + Vendor Management
NGCB-8Annual Independent Cybersecurity Assessment + Reporting + Board Oversight
How this is calculated
Already covered means a mapping runs from a control in AS9100D 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