Skip to main content

Secret rotation and telemetry evidence

This required 22–32-hour integrated package strengthens the existing guided labs. Allocation: lessons/predictions 5–7 hours, control/telemetry experiments 11–17, assessment/repair 6–8. Author estimates require learner timing pilots and are included in the semester workload contract. Reuse the same service and evidence; avoid creating a second portfolio.

Prerequisite bridge​

Bring the preceding module's implementation, risk record and failure observations. Separate assumptions, model results and actual runtime evidence. Review the specific prerequisite named in each lesson before its exercise. Missing runtime tools leave execution evidence pending; a written prediction is not an executed experiment.

Lesson sequence​

  1. Test secret rotation as a state transition.
  2. Preserve diagnostic meaning without collecting everything.
  3. Observe the observer during an incident.

Integrated experiment​

Combine the original threat/control, secret, correlation and alert labs into one synthetic request path. Run normal traffic, credential transition, forbidden access, sensitive sentinel injection, downstream latency and collector outage. Retain positive controls, redacted raw observations and an owned remediation action for each failure. Classify every observation as application, control-plane or telemetry-path evidence; do not turn absence of logs into an authorization success.

Complete the assessment. Original guided labs, security controls, deployment/testing and peer requirements remain mandatory. Use synthetic data and a disposable local environment where supported; no cloud purchase is required by this extension.

Selective resources​

OpenTelemetry sensitive data; Collector security; Google SRE monitoring.