19% of Automotive SPICE (ASPICE) v4.0 you already have
NIST SP 800-171A Rev 3 already covers about 19% of Automotive SPICE (ASPICE) v4.0, leaving
25 of 31 controls as genuinely new work.
Already covered 4
Likely covered 2
New work 25
What is genuinely new work
Nothing in NIST SP 800-171A Rev 3 reaches these. This is the list to scope.
HWE.1Hardware Requirements Analysis
HWE.3Hardware Verification
HWE.4Hardware Qualification Verification
MLE.4Machine Learning Model Testing
SEC.1Cybersecurity Requirements Analysis
SUP.10Change Request Management
SUP.9Problem Resolution Management
SWE.1Software Requirements Analysis
SWE.2Software Architectural Design
SWE.3Software Detailed Design and Unit Construction
SWE.4Software Unit Verification
SWE.5Software Component Verification and Integration Verification
SWE.6Software Verification
SYS.1Requirements Elicitation
SYS.2System Requirements Analysis
SYS.3System Architectural Design
SYS.4System Integration and Integration Verification
Show the 6 you already have
MLE.1Machine Learning Requirements Analysis
MLE.3Machine Learning Training
SUP.8Configuration Management
MLE.2Machine Learning Architecture
SUP.11ML Data Management Support
How this is calculated
Already covered means a mapping runs from a control in NIST SP 800-171A Rev 3 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