NewThe go-live gate: an owner, an approval and a tested stop.See how →
Anthouse
Application security · Shadow IT · Automation governance

Nothing runs without an owner, an approval and a way to stop it.

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 requirements
Passport DEMO-PASSPORT-021

KYC 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
Live · cleared at the gate

Demo passport with made-up data. Try a stop to see how the record changes.

For teams that answer to a regulatorDORANIS2EU AI ActGDPRInternal audit

One list for everything that runs, AI or not.

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.

Illustrative application records
What runsWho owns it?Is it approved?Can you stop it?Seen by
KYC document checkerAI agent · ComplianceOwner namedTeodora NikolovaApprovedStop testedIdentity provider · Firewall
Card dispute robotRPA robot · Card operationsOwner namedGeorgi IvanovWaitingNot testedRobot platform · Collector
Report export scriptPython script · ReportingNo ownerConfirmation neededWaitingNot testedCollector · Firewall
Nightly limits exportScheduled job · TreasuryOwner namedStoyan DimitrovApprovedStop testedCollector
The product

Understand what runs, who owns it and what it can access.

One record from the first signal to the approved passport.

See it in context

Running, but not in the register

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 ↗
Illustrative application records
R

Report export scriptCollector · running process

New
P

Payment file reconciliationLinked application evidence

Review
C

Card dispute robotApplication passport

Registered
Built for security teams

From discovery to a verified decision.

See the evidence behind each application and make the next security decision with context.

What is running?

Discover applications, scripts and automations observed by your connected sources and enrolled devices.

Who is responsible?

Bring ownership, identities and granted permissions together for review.

What changed?

Compare new evidence with approved records and identify what needs attention.

What action was verified?

Keep approvals, execution results and independent verification in one traceable record.

How it works

The evidence does the heavy lifting.

1

Discover

Connect a source or enroll a device. Review what Anthouse finds.

2

Own

Find the responsible person and confirm ownership.

3

Fill

Fill the template from evidence. Answer the remaining questions.

4

Review

Save a revision and record the reviewer’s decision.

5

Prove

Export the approved record with traceable evidence.

Two regulations, two paths

Your register. Your evidence. Your review.

Prepare the records your teams need for DORA and NIS2 review.

DORA

Financial entities

Application passports, ICT assets, providers, contracts and dependencies in one evidence trail.

Discuss your requirements →
NIS2

Essential and important entities

Keep application ownership, risk answers, operational tests and incident records together.

Discuss your requirements →
The inside check

Two weeks on your premises, ending in a written report.

Start with one department and the evidence your tools already hold. Agree the scope, review the findings and leave with a prioritized action list.

Find

Read agreed source metadata and collector observations. Group related signals without losing their origins.

Decide

Confirm owners, review access and identify what can be approved, restricted or stopped.

Prove

Receive application passports, evidence references, open gaps and a written report in your template.

Four responses, from a notice to a stop.

Choose an action with the right scope. Retain the request, approval, execution and independent verification.

1

Notify

Ask the responsible person to review the evidence.

2

Review

Record the owner’s answer and an authorized decision.

3

Restrict

Use a configured provider control against a specific target.

4

Stop

Execute the approved response, verify it and retain recovery evidence.

Integrations

Connect the tools you already run.

Google WorkspaceMicrosoft Entra IDOktaGitHubMicrosoft DefenderCrowdStrike FalconAnthouse Collector
For banks and regulated teams

It runs inside your network.

Plan hosted or on-premises delivery around your infrastructure, data boundaries and security requirements. Keep infrastructure ownership, updates and support access explicit.

  • ✓ Organization-controlled access
  • ✓ Explicit collection policy
  • ✓ Evidence with source references
  • ✓ Scoped integrations and acceptance testing
Questions

Before the first scan.

What does Anthouse discover?

Applications and automations seen by enrolled device collectors and connected identity or security sources. Every observation keeps its source and dates for review.

Will it fill our existing template?

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.

Does a detected app become approved automatically?

No. Discovery, registration, confirmed ownership and approval are separate steps. The passport keeps the evidence and the decisions together.

What does the collector read?

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.

Can we run it inside our network?

On-premises deployment is scoped with your security and infrastructure teams, including connectivity, updates, integrations and acceptance testing.

What do auditors receive?

An application passport, the approved register revision and its evidence references. Internal review can retain drafts and activity; external export uses the reviewed scope.

Get started

See what already runs in your organization.

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 →
What must Anthouse help you govern first?

Anthouse may contact you about early access. Read our privacy notice.