A status page is not a tested fallback | 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 12. Map, example, EX066.

flowchart TD
  G["Evidence gap: no tested fallback sign-in"] --> S["A supplier page says operational"]
  S --> R["That page is not a fallback test"]
  E["Exercise reconnected identity in 25 min"] --> N["That step is part of the restore, not a fallback"]

Being able to sign in again on the restored copy is not a plan for when sign-in itself is gone.

Logical drawing

scenario
    identity provider unavailable
    staff cannot reach any service
    fallback sign-in: not tested
exercise step
    reconnect identity provider: 25 min
        |
        +-- 25 min is a step in the first log
        +-- it assumes the provider can be reconnected
        +-- no fallback product is named

Learning outcomes

After this chapter, you should be able to:

Keep the fallback sign-in untested.
Refuse a supplier status page as that test.
Keep the 25-minute reconnect inside the restore log.

12.1 Reconnection assumes the provider is still there to reconnect

The identity scenario's evidence gap is that Northstar has not tested a fallback sign-in. If the provider is unavailable, staff cannot reach any of the three services. A classmate pastes a supplier status page that says the service is operational and calls the gap closed. A status line is not a fallback, and it is not a test Northstar ran. The exercise did include "reconnect identity provider" at 25 minutes. That step is how the restored portal was signed into during the first log. It does not show what the front desk would do if the provider could not be reconnected at all. The engineer names no fallback product and does not mark the gap as tested.

12.2 Worked example

Lesson table; scroll horizontally to read all columns →

Offering	Question it answers	Decision
Supplier status: operational	The supplier's own notice	Not a Northstar test
Reconnect step, 25 min	A line in the first restore	Keep it as that line
"So fallback sign-in is proven."	A different gap	Refuse
Buy a second identity product tonight	No product is in the file	Do not invent one

Synthetic case. The status page is a classmate's printout. No uptime percentage is added.

Errors and limits

Leaving the fallback untested does not make the 25-minute step unimportant. It keeps that step from answering a question it never asked.

Apply

EX066 — What did 25 minutes show? The identity provider was reconnected in 25 minutes during the restore. A teammate treats a supplier status page, plus that step, as a tested fallback sign-in. What gap remains, and what do you not name?
Show marking criteria
Rubric: 3 = fallback sign-in stays untested; a status page is not that test; the 25 minutes stay a restore step; name no fallback product;; 2 = the gap stays open;; 1 = one of those;; 0 = none.