Chapter 4 — Advanced risk and ethics
Lesson map
Lesson 04 published. Map, example, EX016.
flowchart TD
N0["Learning outcomes"]
N1["4.1 Risk to whom"]
N2["4.2 Duties beyond the organisation"]
N3["4.3 Conflicts of interest"]
N4["4.4 Customer communication"]
N5["4.5 Proportionality"]
N6["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6
N6 --> EX["Worked example"]
EX --> Q["Exercise EX016"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["4.1 Risk to whom"]
N2["4.2 Duties beyond the organisation"]
N3["4.3 Conflicts of interest"]
N4["4.4 Customer communication"]
N5["4.5 Proportionality"]
N6["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> Q["EX016"]
[Learning outcomes]
|
v
[4.1 Risk to whom]
|
v
[4.2 Duties beyond the organisation]
|
v
[4.3 Conflicts of interest]
|
v
[4.4 Customer communication]
|
v
[4.5 Proportionality]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX016]
Learning outcomes
You will (1) weigh risks to customers and third parties; (2) handle conflicts of interest; (3) apply ethics to enforcement choices.
4.1 Risk to whom
Most of the provider's decisions shift risk between groups. Ingress filtering mainly protects other networks from spoofed traffic originating from Fenwick Valley customers, while carrying a small risk of disrupting customers with unusual setups. Route validation protects Fenwick Valley's customers from mis-originated routes but could cut them off from legitimate destinations if records are wrong. Marta lists, for each decision, who bears the risk and who receives the benefit. Making this explicit helps directors see when they are asking customers to accept a small risk for a wider public benefit.
4.2 Duties beyond the organisation
Internet providers sit in a shared system where each network's behaviour affects others. A provider that allows spoofed traffic contributes to attacks on third parties, even if its own customers are not harmed. Marta argues that a responsible provider has duties to the wider internet, reflected in long-standing recommendations such as RFC 2827. Professional ethics, which emphasise avoiding harm to the public, support this view. The directors agree in principle but ask for evidence that filtering will not disrupt customers before committing to it.
4.3 Conflicts of interest
Marta notices a potential conflict: one director also advises a vendor selling a filtering appliance. She raises it with Prof. Brooks and the provider's chair, who ask the director to step back from that decision. Conflicts are not wrongdoing in themselves, but undisclosed conflicts damage trust in decisions. Marta also discloses her own position: her placement assessment depends partly on producing a recommendation, which could tempt her to recommend change for its own sake. Stating this openly invites others to challenge her if her analysis seems biased.
4.4 Customer communication
Enforcement that affects customers should be explained before it happens. Marta drafts a customer notice explaining that the provider will begin dropping traffic with forged source addresses, why this protects the internet, how few customers are likely to be affected and how to contact support if something stops working. She avoids technical jargon and alarming language. Customers who understand a change are less likely to be angry if it affects them, and support staff can answer questions consistently from a prepared script.
4.5 Proportionality
Ethical enforcement is proportionate: the response matches the risk. Rejecting all invalid routes immediately would be disproportionate while the provider has no experience of how often records are wrong. Marking invalid routes with lower preference first is proportionate, protecting against most mis-origination while learning about errors. Similarly, filtering spoofed traffic is proportionate because legitimate customer traffic almost never uses addresses outside the customer's range. Proportionality gives a principled way to choose between strict and gentle options rather than relying on instinct.
Worked example
Marta's risk table lists who bears risk and who benefits for three decisions; the customer notice is approved by the support manager.
Synthetic case. The provider and people are synthetic.
Errors and limits
Ignoring third-party harm because it does not affect one's own customers neglects shared responsibility.
Exercises
- EX016 — Benefit of ingress filtering. Who mainly benefits from Fenwick Valley's ingress filtering? Rubric: 3 = other networks targeted by spoofed traffic;; 2 = others;; 1 = own customers;; 0 = none.
- EX017 — Conflict handling. How was the director's conflict handled? Rubric: 3 = disclosed, director stepped back from decision;; 2 = stepped back;; 1 = ignored;; 0 = none.
- EX018 — Own bias. What bias did Marta disclose about herself? Rubric: 3 = placement assessment tempts recommending change;; 2 = assessment;; 1 = vague;; 0 = none.
- EX019 — Proportionate validation. Why mark invalid routes before rejecting them? Rubric: 3 = learn error rate first; proportionate;; 2 = gradual;; 1 = faster;; 0 = none.
- EX020 — Customer notice content. Name three elements of the customer notice. Rubric: 3 = what changes, why, how to get help or how few affected;; 2 = two;; 1 = one;; 0 = none.
Synthesis
Advanced risk and ethics weigh who bears risk, recognise duties beyond the organisation and choose proportionate enforcement.
Continue studying — chapter 04 of 12
← Chapter 03 (draft) · Course chapter index · Chapter 05 (draft) →