Q1 (1.5 points)
https://knobit.org/id/task/dsec-access-design/Q1
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/task/dsec-access-design/Q1 |
| rdfs:label | Q1 (1.5 points) en |
| schema:hasPart | dsec-access-design Q1: agency controls tagged by type of data security |
| schema:hasPart | dsec-access-design Q1: a tool named for each agency control |
| schema:hasPart | dsec-access-design Q1: implementation, performance and risk metrics |
| schema:identifier | Q1 |
| schema:position | 7 |
| schema:text | The agency's controls and the metrics, 0.5 each. (a) agency_controls tag each control with the type of data security it is, with at least three of the five types facility, device, credential, document and content present and none mis-tagged (accounts and MFA are credential, agency laptops device, the feed file document, what the portal shows content, the agency's premises facility; portal exposure is network). (b) Each control names a tool that implements it: identity management for the accounts, firewall or VPN for the portal, encryption for the file, masking or row-level security for content, endpoint management or anti-virus for devices. (c) metrics give one implementation, one performance and one risk metric, each with a formula and a target the access design can move (e.g. share of restricted columns with a column_access entry; hours from an agency leaver to the account disabled; persons holding both sides of an SoD rule). en |