Honest limits
What this product does not claim.
This page carries the same weight as the capability page. Every line is a limit the product enforces on itself, not a disclaimer bolted on at the end.
It does not
Each of these is refused by design, not merely unimplemented.
- No blended score
- Severity and confidence stay separate. No single trust number that hides which is which.
- No clearance verdict
- A clean scan is never a statement that a target is secure.
- No absence proof
- A timeout or an unreachable record is reported as a coverage gap, never as a pass.
- No self-service signup
- Access is administrator-provisioned. There is no public registration.
- No autonomous action
- Remediation is prepared for a human. Nothing is applied automatically.
- No customer claims
- No logos, no testimonials, no case studies, because there are none to show.
Known gaps, stated plainly
Naming these is cheaper than being caught by them.
- Field accuracy
- Precision and recall are measured against a controlled corpus, not the whole internet.
- Physical inspection
- A phone camera is not TSCM equipment. Confidence stays capped accordingly.
- Imported documents
- A declared component list proves what a producer declared, not what is deployed.
- Partial modules
- Some modules are honestly partial and say so on their own surface.
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.