Breakglass
Incidents
Onboarding · Mercy Valley Community Hospital Simulated hospital Connecting…

From connected to protected, in five checks

Day one is the same loop as every other day: Breakglass looks at the exploited flaws that are already listed and still inside their deadline, and shows what it would close.

  1. 01
    Connect the inventory
    5 internet-facing assets and 19 components, the portal's from its lockfile. Declared appliances (firewall, endpoints, browsers) are matched too, but only reported.
    Done
  2. 02
    Connect the edge
    The reverse proxy in front of those services. Breakglass checks it can read state through the credential proxy, without ever holding the admin token itself.
    To do
  3. 03
    Review the credential policy
    6 scoped rules; the allow-all rule is deleted; shutdowns are denied.
    Done
  4. 04
    Confirm critical routes
    12 routes patients depend on are never on the may-disable list.
    Done
  5. 05
    First evaluation
    Check every KEV entry still inside its federal due window against the estate, right now.
    Needs the orchestrator running.
    To do
Go to the dashboardReview the policy