Security and live operations

Controls you can see while the site is live

Scoped access (RBAC), audit-backed evidence, the audit trail, controlled rollout and rollback, bounded recovery—plus diagnostics when something looks off. Same app as incident review and handover, not a bolt-on portal.

Access, evidence, audit, and recovery shown together in one working view.

Under Security & Trust · operational controls

Scoped access / RBAC

Who can do what

Roles and scopes line up with org, site, and device—so when you add users or sites, it stays obvious who can change policies, devices, or rollout.

Scope enforced where the app enforces changes—not only what you see on screen
Default is no access until a role grants it
People and automation get different credentials; each gets the minimum it needs
Edge and cloud talk over an authenticated link—no open pipe
Risky steps can wait on approval before they hit a live site
Diagram: site, edge, cloud app, and where RBAC applies during rollout.

Where the site, edge, and app meet—so review and rollout stay in one picture.

Evidence controls

Evidence integrity

Audit-backed evidence means you can stand behind what you review: how it was captured, that handling stayed consistent, and what you kept for later review.

Checks from capture through handoff—breaks show up as errors, not missing rows
Failed steps stay on the record instead of vanishing
Retention set so a deployment review weeks later still makes sense
Incident review

Reviewers see the same evidence path and retained clips or artifacts—so the story does not change between the floor and sign-off.

Traceability

What gets logged and why it matters

When you run more than one site, you need an audit trail you can read: important actions, evidence touches, and rollout decisions tied to real people and times.

Record of important actions in order—they do not get rewritten after the fact
Evidence access logged when reviewers need to know who looked
Emergency access for a short window when you must—still written down
Rollout and sign-off tied to who changed what
Access, evidence, and audit trail in one Edgentik view.

Access, evidence, and audit trail in one place—still the same app.

Recovery controls

How risky changes stay controlled

After bring-up, you still need to know which stage you are in, when an apply failed, and how to roll back to last known good without inventing steps in the field. Recovery stays bounded: clear stages, a real rollback path, and the same audit trail as the change.

Rollout stages listed in the app—you see what is running
Rollback to last known good when apply fails or the site needs it
Status reflects what the edge reported back
Recovery steps you can follow in the app, not from memory
Recovery next to rollout in one record
Edgentik rollout and rollback states and last known good.

Rollout and rollback as statuses you can read in the product.

Review surface

How these controls show up together

Access, evidence, audit, and recovery shown together—same app as day-to-day operations, with room for handover when you pass the site to the next reviewer.

  • Scoped access (RBAC)

    Open only the sites and devices that role should see.

  • Audit-backed evidence

    Incidents tie to clips and context you can defend in review.

  • Audit trail

    See who changed rollout, policy, or evidence when it mattered.

  • Controlled rollout / rollback

    Bounded recovery: stages, last known good, and what to do next—without leaving the product story.