@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix edu: <https://knobit.org/def/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix schema: <https://schema.org/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<https://knobit.org/id/task/dsec-access-control/C2> a edu:Question ;
    rdfs:label "C2 (2 points)"@en ;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/> ;
    owl:sameAs <https://bitbucket.org/reffa/ontology/id/task/dsec-access-control/C2> ;
    schema:hasPart <https://knobit.org/id/register/data-security#SE-303>,
        <https://knobit.org/id/register/data-security#SE-304> ;
    schema:identifier "C2" ;
    schema:position 2 ;
    schema:text "Segregation of duties, 1 each. (a) PAY_OPS holds create_payment and approve_payment, which SD-001 forbids together; the payments operator can create and approve the same transfer. (b) The conflict is resolved by splitting the roles - approve_payment moved to a separate role held only by the payments approver - not by adding monitoring or a report alone."@en .

edu:Question rdfs:label "Question"@en,
        "Küsimus"@et .

<https://knobit.org/id/register/data-security#SE-303> rdfs:label "dsec-access-control C2: the payments operator can create and approve"@en .

<https://knobit.org/id/register/data-security#SE-304> rdfs:label "dsec-access-control C2: the conflict split into roles, not only monitored"@en .

