What did the product accept?
Preserve the check type, current status, and limits used for the decision.
Speed security and ops review with checkable decisions.
When a product accepts a trust result, keep a reusable record of what was checked and whether it is still current. Security and operations teams can review that decision without rebuilding it from scattered tickets.
The approval record behind the logs
Is the record still current?
Show whether the proof was later revoked or expired after the original decision.
What stays in host logs?
Use NEUS for the trust-decision record. Keep Datadog, Splunk, or your security tools for full telemetry.
Speed security and ops review in the NEUS productHow it works
Add the check, save the result, review, revoke
- 1Record the decisionRequire a NEUS proof check on the protected path.
- 2Capture the decisionStore the accepted receipt reference with the access event.
- 3Open review from the receiptLet security open the current receipt without exposing the full source file.
- 4Act on revocationRefuse new actions when status changes; investigate with both receipt and logs.
Trust receipt
Current
One check. Reusable everywhere it is accepted.
SubjectAcme Ops | Organization
CheckOrganization
ScopeAccess | Payout
StatusActive
Expires2026-12-01
Connected apps confirm status before access without the full source file.
Integration options
Use the path closest to your first protected decision.
- Hosted check
- Start without building a custom screen
- JavaScript
- Add the check to a product backend
- HTTP
- Check a receipt from any service
- React
- Drop the flow into an existing interface
- Assistant setup
- Bring trust checks into developer tools
What stays true
Clear checks at the moment they matter.
- A clear decision record beside existing logs
- Ideal companion to analytics and security buyers
- People and assistants share one review record
Review and audit questions
How decision receipts sit beside host logs in an incident.