Map BCBS 239 to controls

https://knobit.org/id/activity/GO-4

dcterms:license	https://creativecommons.org/licenses/by/4.0/
owl:sameAs	https://bitbucket.org/reffa/ontology/id/activity/data-governance/04-regulatory-mapping
rdfs:comment	Stage 4 (Regulatory mapping (BCBS 239)) of the data-governance skill: produces 04-regulatory/control-matrix.yaml and passes the stage's validation gate. en
rdfs:label	BCBS 239 põhimõtete vastendamine kontrollimeetmetele et
rdfs:label	Map BCBS 239 to controls en
requires knobit	Recognises a regulatory principle with no control
requires knobit	Recognises a regulatory principle dropped without reason
requires knobit	Recognises a control with no evidence
requires knobit	Recognises control evidence owned by nobody
requires knobit	Recognises stale control evidence
requires knobit	Recognises a control tested for design only
requires knobit	Recognises a control mapped to a principle it cannot address
requires knobit	Recognises a manual step outside the control matrix
requires knobit	Recognises a control operating no internal standard
requires knobit	Recognises a control owner without authority over the process
requires knobit	Recognises a control in self-review
requires knobit	Recognises a control slower than the report it protects
requires knobit	Recognises automation evidenced by a manual artefact
requires knobit	Recognises a control covering part of the report's population
requires knobit	Recognises a reference to a principle outside the scope
requires knobit	Designs a control over a manual adjustment
requires knobit	Explains design and operating effectiveness of controls
requires knobit	Explains control evidence and its currency
requires knobit	Explains manual steps in report production as a control risk
requires knobit	Explains the attributes of a control
requires knobit	Explains the BCBS 239 principles
schema:position	4

Used by

consists of	Data governance