Security evidence you can inspect, challenge, and act on

Authorized-only deployment. Aegis records what was observed on targets you are allowed to test, and keeps the evidence next to every finding.

  • Digital posture 12
  • Device and network privacy 5
  • Physical privacy 8
The 25 checks this instance runs, grouped by family: 12 digital posture, 5 device and network privacy, 8 physical privacy. Drawn from the live check registry at render time. See every check

What this instance does

Each one names the evidence behind it. None is a promise about the future.

25 registered checks on this instance (12 + 13)

Passive digital checks

TLS, headers, DNS, cookies and CORS, observed without probing or disruption.

See every check

Reviewable outputs

Source, method, timestamp, severity, confidence and coverage, recorded together and traced back to the finding.

See what is exported

Physical privacy

A guided, authorized inspection of a room. Confidence is capped because a phone is not specialist equipment.

How inspections work

Evidence intake

Add OpenAPI, SARIF, CycloneDX and SPDX files. They are previewed locally first.

Read the method

Who it is for

Four readers, one artifact: a report a person can check.

Non-technical owner

See what was observed on your own sites, in plain words, without running a tool.

Small and medium business

Keep findings and the evidence for them in one place instead of a spreadsheet.

Security team

Review severity and confidence separately, then retest after a fix.

Consultant or accounting firm

Hand a client a report with its sources, method and coverage attached.

Read the method

A finding, as the product renders it

An example, built from the shape a real finding has. Not a customer's data.

Security headers

Severity HighConfidence High

Source
The response headers the target published.
Method
Passive observation. Nothing was sent but the request itself.
Timestamp
Recorded when the check ran, not when this page rendered.

Severity and confidence are separate. A serious impact does not make a weak signal stronger.

Read how a finding is built

The rules on every assessment

Authorized-only, evidence-based, and approved by a person. Five guarantees hold throughout.

The five guarantees

Evidence-grounded
No raw source document retention in the assessment store.
Severity ≠ confidence
High impact does not inflate weak signals.
Coverage stated
Timeouts are coverage gaps, never clean results.
Authorization before measurement
Fails closed when the scope is unclear.
Local-first
No analytics pixels, no cloud sync.

Read the trust model

Questions people ask first

What can I measure?

This instance exposes passive digital posture checks, local network and device context, physical privacy guidance, and bounded evidence intake. The capabilities page is the source of truth.

Does Aegis make a security decision for me?

No. Aegis records evidence, severity, confidence and coverage. A person reviews the report and approves any state-changing action.

Can I try it?

Access is administrator-provisioned on this instance. Sign in to continue, or contact the team to discuss an authorized deployment.

Make evidence easier to review

Talk with us about an authorized deployment and the checks your team needs.

Aegis does not use analytics or third-party scripts.

How to read this

Authorized-only · evidence-based · point-in-time. Aegis cannot guarantee the absence of weaknesses or hidden devices. On this machine, live external HTTP/TLS may be network-blocked and shown as an honest coverage gap. Severity and confidence are kept separate. Finished assessments persist in the encrypted store while durable storage is bound. A theme choice may persist in this browser. Export remains available for a copy you can take with you.