DEMO-PASSPORT-021KYC document checker
AI agent · Compliance
Identity provider · Firewall- Who owns it?Owner namedTeodora Nikolova
- Is it approved?ApprovedApproved revision retained
- Can you stop it?Stop testedVerified test evidence retained
Find the scripts, robots, scheduled jobs and AI agents your security tools can see. Confirm an owner, record the approval and test the stop. Keep the passport and evidence in your register.
Or get a free First Look from public records →SaaS or on-premises · Scoped to your data and network requirementsDEMO-PASSPORT-021AI agent · Compliance
Identity provider · FirewallDemo passport with made-up data. Try a stop to see how the record changes.
The same three questions for a script, a robot, a scheduled job and an AI agent. A stamp means the answer is on record. A dashed slot means it is still missing.
| What runs | Who owns it? | Is it approved? | Can you stop it? | Seen by |
|---|---|---|---|---|
| KYC document checkerAI agent · Compliance | Owner namedTeodora Nikolova | Approved | Stop tested | Identity provider · Firewall |
| Card dispute robotRPA robot · Card operations | Owner namedGeorgi Ivanov | Waiting | Not tested | Robot platform · Collector |
| Report export scriptPython script · Reporting | No ownerConfirmation needed | Waiting | Not tested | Collector · Firewall |
| Nightly limits exportScheduled job · Treasury | Owner namedStoyan Dimitrov | Approved | Stop tested | Collector |
One record from the first signal to the approved passport.
Review scripts, robots and local apps found by your sources. Use your organization’s AI model to compare captured evidence and review suggested groups with confidence scores, while retaining every original source.
Request a walkthrough ↗Report export scriptCollector · running process
NewPayment file reconciliationLinked application evidence
ReviewCard dispute robotApplication passport
RegisteredSee the evidence behind each application and make the next security decision with context.
Discover applications, scripts and automations observed by your connected sources and enrolled devices.
Bring ownership, identities and granted permissions together for review.
Compare new evidence with approved records and identify what needs attention.
Keep approvals, execution results and independent verification in one traceable record.
Connect a source or enroll a device. Review what Anthouse finds.
Find the responsible person and confirm ownership.
Fill the template from evidence. Answer the remaining questions.
Save a revision and record the reviewer’s decision.
Export the approved record with traceable evidence.
Prepare the records your teams need for DORA and NIS2 review.
Application passports, ICT assets, providers, contracts and dependencies in one evidence trail.
Discuss your requirements →Keep application ownership, risk answers, operational tests and incident records together.
Discuss your requirements →Start with one department and the evidence your tools already hold. Agree the scope, review the findings and leave with a prioritized action list.
Read agreed source metadata and collector observations. Group related signals without losing their origins.
Confirm owners, review access and identify what can be approved, restricted or stopped.
Receive application passports, evidence references, open gaps and a written report in your template.
Choose an action with the right scope. Retain the request, approval, execution and independent verification.
Ask the responsible person to review the evidence.
Record the owner’s answer and an authorized decision.
Use a configured provider control against a specific target.
Execute the approved response, verify it and retain recovery evidence.
Plan hosted or on-premises delivery around your infrastructure, data boundaries and security requirements. Keep infrastructure ownership, updates and support access explicit.
Applications and automations seen by enrolled device collectors and connected identity or security sources. Every observation keeps its source and dates for review.
Anthouse fills the supported fields from the evidence it has and shows their source. Business purpose, ownership, risk and other organization facts remain visible for a person to confirm.
No. Discovery, registration, confirmed ownership and approval are separate steps. The passport keeps the evidence and the decisions together.
Device and application metadata permitted by your collection policy. README and license collection can be enabled separately. It does not collect source files, messages or passwords.
On-premises deployment is scoped with your security and infrastructure teams, including connectivity, updates, integrations and acceptance testing.
An application passport, the approved register revision and its evidence references. Internal review can retain drafts and activity; external export uses the reviewed scope.
Request a two-week inside check. We’ll agree the sources, department, data boundaries and written report with your team.
Prefer to talk? Contact us →