Offline by design
Assessment, investigation and report review work without an external service.
Software assessment update assurance for defence evaluation
Understand the software being delivered, observe its tested behaviour, and retain the evidence behind its security assessment.
Review what suppliers deliver and what each update changes inside your own enclave, with a human making the call.
Assessment posture
The assessment system is designed around the conditions in which defence evaluators work.
Assessment, investigation and report review work without an external service.
Starts from the software that was delivered. Source and build records are optional extras.
Analysts choose and run the tests. SENTINEL never launches attacks on its own.
An authorized person keeps the deployment decision. There is no autopilot.
The evaluator's problem
Dependency lists, scanner output, behaviour records and manual notes rarely answer them together. SENTINEL keeps them in one assessment record.
Is this the exact release that was assessed?
Which components can be identified, and what is still uncertain?
Which advisories may apply to those components and versions?
What happened during the recorded installation and test scenarios?
How could access, weaknesses and conditions combine to affect a protected asset?
What differs from the last assessed release, and does it matter?
Attack-path analysis
An advisory match says a component may be affected. It does not say whether an attacker can reach it, what access they would need, or what it would mean for a protected asset.
A vulnerability ID alone never creates an entry point, a privilege or an impact.
A blocked route is recorded as blocked under those conditions.
Validating a single step never silently marks the whole path demonstrated.
Analysts prioritise by evidence quality, access needed and consequence.
End-to-end workflow
An incomplete stage stays incomplete. A quiet run, missing evidence or a failed reproduction never quietly becomes a clean result.
Evidence change
Reports and structured outputs come from the same assessment record, so what a reviewer reads is what the tools found.
Evidence bundles can be signed so tampering is detectable. A signature protects integrity; it does not make every recorded claim true.
Release comparison
A new finding may come from new knowledge about unchanged software. SENTINEL does not call that a newly introduced defect.
Deployment posture
SENTINEL assumes restricted connectivity from the start. Assessed software, customer evidence and results do not need to leave your environment.
Assessment, investigation, report generation and evidence review run with no external service or hidden cloud dependency.
Advisory data, tools and policy arrive through a reviewed offline process with recorded provenance.
Submitted software runs in disposable environments with no route to controller credentials or operational networks.
Submission, analysis, administration and review are distinct roles, configured to approved procedure.
No implicit upload of assessed content. Secrets are shown masked. Exports are controlled.
Modified bundles fail their integrity check. Every disposition and exception is attributable.
Engagement
Workflow benefit is a hypothesis until measured in your procedure. No performance, detection-rate or time-saving figures are claimed.
Trust boundaries
Evaluation briefing
A briefing walks evaluators through the workflow on a synthetic demonstration target and agrees what a representative evaluation would measure.