jperezduerto.info
Security in depth · Unit 26 · Lesson 4 of 4
Observe the whole access path
Build a careful explanation from gateway and destination records with different meanings.
Helpful before thisPivoting, proxies, and network boundaries
After this lesson you can
- Distinguish a correlated service operation from proven attribution to a particular person.
One idea. One situation. One reasoned decision.
How it works
An administrative operation can cross a client, gateway, identity provider, network boundary, and destination. No single log necessarily explains the entire action. Preserve useful correlation information and time context across the path while avoiding unnecessary sensitive content. When an event is missing, identify the coverage gap rather than assuming the operation did not occur.
Join records without inventing an actor
A fictional administrative gateway forwards approved work through a service identity. All supplied timestamps use UTC, but clock offsets have not been measured.
| Record | Observation |
|---|---|
| O1 | Gateway: Mara authenticated; session S8 |
| O2 | Gateway: S8 forwarded request R7 to the records service |
| O3 | Destination: R7 updated document Q as relay-service |
Worked decision: the shared request identifier links the recorded forwarding event to the recorded destination update, assuming its uniqueness and propagation have been validated. O3 attributes the operation to the service identity. It does not independently identify the human who initiated that specific action.
To assess human attribution, request the documented mapping from authenticated session to approved action and the evidence that the mapping cannot be casually overwritten. Mara’s authentication alone does not prove she authorized every operation later associated with that session.
Preserve original timestamps and their clock context; matching displayed times is weaker than a verified correlation relationship. Log the minimum useful action, resource identifier, outcome, and approved attribution context. Avoid storing credentials or document contents merely to make a record look detailed. The final explanation should separate the observed chain from the still-unverified human decision.
The key distinction: Connection establishment and resource operations are different events.
Check yourself
No timer. No penalties. Read the explanation and try again whenever you like.
This lesson’s questions have changed. Your reading progress is saved; review the updated questions.
-
Which statement stays within the evidence in O1-O3?
Show the answer
Correct answer: R7 links a recorded forward to an update by relay-service; human approval needs further attribution evidence. This preserves the recorded service actor and the conditional correlation link while identifying the missing proof of the human decision.
Try it
- WriteWrite one supported sentence and one uncertainty using O1-O3. Propose an attribution field or mapping record without adding credentials or document contents to logs.