Chapter 10 — Engineering ethics and safety
Lesson map
Lesson 10 published. Map, example, EX028.
flowchart TD
N0["Learning outcomes"]
N1["10.1 Duties"]
N2["10.2 Privacy and monitoring"]
N3["10.3 Safety of actions"]
N4["10.4 Honesty"]
N5["10.5 Conflicts"]
N6["10.6 Raising concerns"]
N7["10.7 Professional codes"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX028"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["10.1 Duties"]
N2["10.2 Privacy and monitoring"]
N3["10.3 Safety of actions"]
N4["10.4 Honesty"]
N5["10.5 Conflicts"]
N6["10.6 Raising concerns"]
N7["10.7 Professional codes"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX028"]
[Learning outcomes]
|
v
[10.1 Duties]
|
v
[10.2 Privacy and monitoring]
|
v
[10.3 Safety of actions]
|
v
[10.4 Honesty]
|
v
[10.5 Conflicts]
|
v
[10.6 Raising concerns]
|
v
[10.7 Professional codes]
|
v
[Worked example] --> [Exercise EX028]
Learning outcomes
You will (1) apply engineering ethics to security operations; (2) balance monitoring with privacy; (3) handle conflicts between speed and safety; (4) report concerns responsibly.
10.1 Duties
Engineers owe duties to the public, employers and colleagues. In a SOC, monitoring protects people but also observes them. Ethical practice means collecting what the purpose requires and no more.
Duty to the public includes the customers whose accounts are protected and whose data passes through monitored systems. Duty to the employer means doing competent, honest work. Duty to colleagues means not monitoring them beyond what policy permits. Collecting only what the purpose requires limits the harm if monitoring data is ever misused or leaked.
10.2 Privacy and monitoring
Staff and customers have privacy interests. Lindqvist's monitoring policy tells staff what is monitored and why; SOC access to content (such as email bodies) needs case approval.
Telling staff what is monitored is both fair and practical: people who know the rules are less likely to feel betrayed when monitoring reveals a problem. Metadata, such as who emailed whom and when, is less intrusive than content. Requiring case approval before reading content keeps the more intrusive step tied to a specific, justified need.
10.3 Safety of actions
Response actions can harm operations: blocking a network might stop delivery trucks' route updates. Engineers consider side effects and use approved playbooks.
Lindqvist's trucks depend on network access for route and delivery updates, so cutting a network segment during a response could strand drivers or delay shipments. Playbooks list known dependencies for each action and who must be told before it is taken. Where risk is high, a narrower action, such as blocking one address, is tried before a broad one.
10.4 Honesty
Reports must not hide failures, such as a missed detection, even when embarrassing. Hiding them prevents learning.
A missed detection is information: it shows a gap in data, logic or process. Reporting it lets the team fix the gap and lets managers judge risk accurately. Concealing it leaves the gap open and erodes trust when it surfaces later, which it often does during the next incident's review. At Lindqvist, missed detections appear in the monthly report with what was changed afterwards, so the same gap is visibly closed rather than quietly forgotten.
10.5 Conflicts
When a manager asks for monitoring of one employee without an investigation request, Amara declines and refers to policy and HR process.
Monitoring a single employee without a formal request could serve a personal dispute rather than a security need and may break employment law or the monitoring policy. Amara does not judge the manager's motives; she explains the process and points to HR, which can open an investigation if one is warranted. She records the request and her response.
10.6 Raising concerns
If a practice seems unsafe or unlawful, engineers raise it through defined channels, documenting facts.
Defined channels include the line manager, the security lead, the compliance team and, where these fail, any whistle-blowing route the organisation provides. Documenting facts rather than opinions keeps the concern specific and checkable. Raising it early, before harm occurs, gives the organisation a chance to fix the practice quietly. Amara learns where Lindqvist's whistle-blowing policy is published during her first week. Retaliation against someone raising a concern in good faith is itself a breach of most codes and many laws.
10.7 Professional codes
Engineering and computing bodies publish codes stressing public good, competence and honesty; Amara reads her university's code during induction.
Codes are short and general, so they guide judgement rather than replacing it. Amara notes three points relevant to her placement: act within her competence, be honest about results and limits, and put public safety ahead of convenience. She refers back to them when the monitoring request in her placement tests those principles. Membership bodies can discipline members who breach them, which gives the codes weight.
Consent and transparency
Customers are told in the portal's privacy notice that login activity is logged for security. Transparency does not replace minimisation, but it lets people understand monitoring and complain if it is misused. The SOC reviews the notice with legal staff each year so it matches real practice.
Worked example
During the portal incident, a colleague suggests blocking the whole 203.0.113.0/24 range permanently. Amara notes that the range belongs to a cloud provider also used by a logistics partner. Paolo agrees to a temporary block with monitoring and a review after 24 hours, documented in the ticket.
Synthetic case. The situation and people are invented.
Errors and limits
Ethics guides judgement but does not give automatic answers; discuss hard cases with supervisors.
Exercises
- EX028 — Minimal collection. What does "collect what the purpose requires" mean in a SOC? Rubric: 3 = monitor for defined purpose, no extra content without approval; 2 = partial; 1 = collect all; 0 = none.
- EX029 — Declining a request. Why did Amara decline monitoring one employee? Rubric: 3 = no investigation request; refer to policy and HR; 2 = partial; 1 = complied; 0 = none.
- EX030 — Range block. Why was the permanent block rejected? Rubric: 3 = range shared with partner; temporary block with review instead; 2 = partial; 1 = blocked; 0 = none.
Synthesis
Ethical SOC engineering limits monitoring to its purpose, weighs side effects of actions and reports honestly.
Continue studying — chapter 10 of 50
← Chapter 09 (draft) · Course chapter index · Chapter 11 (draft) →