A decision-list line is not an owner in the listing | Rapid course Security governance, risk and compliance

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Lesson map

Lesson 07. Map, example, EX061.

flowchart TD
  N["Listing prints NONE"] --> L["Relay and roster go on the director's list"]
  L --> W{"Did someone type a team name into the lab?"}
  W -->|Yes| R["Refuse. The print still says NONE"]
  W -->|No| K["The list is a request for a later decision"]

Asking for an owner does not fill the owner field.

Logical drawing

lab_deps.py
    email relay: owner NONE
    roster spreadsheet: owner NONE
    shared by all three: ['identity provider']
director's decision list
    owners still to be named
        |
        +-- "IT will look at it" is not the owner cell
        +-- no personal name is invented
        +-- the relay is not reconfigured

Learning outcomes

After this chapter, you should be able to:

Keep NONE until an owner is written into the listing's facts.
Refuse a spoken team name as that owner.
Leave the relay and the spreadsheet unedited.

7.1 The list asks. The print has not changed.

Chapter 3 put the email relay and the roster spreadsheet on the operations director's decision list because both owners print NONE. Chapter 4 then named "owners for the email relay and roster" among the quarter's outcomes. A classmate types IT beside the relay and says the outcome is met. IT is already the owner of other components. It is not what the program printed for these two. A sentence in a meeting is not a new run of lab_deps.py. The engineer invents no person's name, does not reconfigure the relay, and does not edit the spreadsheet. The identity provider remains the only component shared by all three services.

7.2 Worked example

Lesson table; scroll horizontally to read all columns →

Claim	Source	Decision
Relay owner is `NONE`	The verified listing	Keep it
"Put IT on the relay; IT owns the web host."	A different row	Refuse the copy
Roster owner is `NONE`	The same listing	Keep it
"We discussed an owner, so the cell is filled."	Talk, not a new print	Refuse

Synthetic case. No colleague is given a personal name in order to fill either cell.

Errors and limits

The decision list is still the right place to ask. Closing it in the margin does not create the appointment the director has not written.

Apply

EX061 — Whose name went into the cell? The quarter's outcomes include owners for the email relay and the roster. A teammate writes IT on the relay because IT owns the web host. What does the listing still print, and what must the engineer not change?
Show marking criteria
Rubric: 3 = both still print NONE; a spoken or copied team name is not that cell; do not reconfigure the relay or edit the spreadsheet; invent no personal name; the identity provider stays the only component shared by all three;; 2 = NONE stays and the relay is not reconfigured;; 1 = one of those;; 0 = none.