AAK-ADMT-002: Developer documentation does not name the categories of training data
- Severity
- MEDIUM
- Category
- Legal Compliance (
legal-compliance) - Scanner
agent_audit_kit/scanners/admt_documentation.py- Auto-fixable
- No.
- SARIF name
AdmtNoTrainingDataCategories
What it detects
Developer documentation exists for a declared covered-domain decision surface but does not describe the categories of data, including personal data, used to train the system. C.R.S. 6-1-1702(1)(b) requires that description, to the extent known, where the technology is one the statute covers. Evidence toward the duty, not a determination that it applies.
How to fix
Add a section describing the categories of training data, including any personal data, to the extent known. C.R.S. 6-1-1702(1)(b) asks for categories rather than the data itself, so this is compatible with the trade-secret protection subsection (1) preserves.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-ADMT-002
Limitations
Passes as soon as the documentation contains training data, training set, training corpus, data used to train, categories of data or trained on, and does not check that any category of data is named: Training data: not disclosed satisfies it.
References
No external references are recorded for this rule.
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-ADMT-002.md: the page then shows that text, with the registry reference appended under it.