TRUST & SECURITY

Your network.
Your call.

Findavi runs on your site, under permissions you approve. You decide what it can see, what it can change, and when it must wait for a person.

See how your data is handled ↓See Findavi in action

DATA & ACCESS

On your site.
Under your control.

Your team approves where the appliance connects and which devices it can reach.

Local analysis. Encrypted storage.: Findavi’s AI runs on the appliance. The network data it collects stays on site. Device records, traffic records, findings, and firewall keys are stored encrypted. No outside AI service processes this network data.
Firewall access has limits.: Findavi’s firewall account can add and remove its own rules. It cannot change other rules. Your administrators control its keys.
Actions leave a record.: Findavi logs each firewall rule and its approval. Autonomous actions run within limits your team approves in advance.
Your sign-in rules apply.: Findavi works with your single sign-on. We confirm the integration before deployment.
Updates are checked before installation.: Findavi checks the signature on its updates and rejects an update if that check fails.
Coverage depends on the connection.: Findavi sees the traffic that crosses its monitoring point. We agree the connection and explain what remains out of view.
Confirm your firewall model and software.: We check support for your equipment before Findavi acts.
View firewall integrations
Cisco, Fortinet, Aruba, Extreme Networks, Check Point, Palo Alto Networks, Juniper Networks, SonicWall, Sophos, WatchGuard, Barracuda Networks, Forcepoint, Hillstone Networks, Sangfor, pfSense (Netgate), and OPNsense (Deciso).

APPROVALS

Choose when Findavi acts.

Set the mode for each device and supported action.

Observe: Review findings and recommendations. Findavi makes no changes.
Approve: A person on your team approves the proposed action before it runs.
Autonomous: Findavi acts within the device and action limits you approve in advance.

RESULT CHECKS

Blocked the attack?
Check the service, too.

We agree both checks before any change. A camera can answer on the network and still not record.

Did the security action work?

Retest the problem. For example, confirm the attacking connection is blocked.

Does the device still do its job?

Check the required service. For a camera, confirm a new recording reaches the approved recorder.

Findavi records the action and both results. A failed check or missing evidence keeps the issue open for follow-up.

Read the camera attack account

STOPPING & RECOVERY

You can stop an agent.

Your team can stop or switch off a Findavi agent at any time. Supported recovery actions, including restoring previous settings, require a person’s approval.

Before a change, agree how to stop, who takes over, and which recovery steps are supported. Automatic rollback is used only when it is available, tested, and approved for that action.

Your service owner defines the service check. Some checks need an engineer, a physical inspection, or the equipment vendor. A software check alone cannot confirm physical safety.

BEFORE DEPLOYMENT

Agree the details before connecting.

Accounts and permissions: Which accounts Findavi needs, what each can do, and who controls them.
Credentials: How passwords and keys are stored, changed, and revoked. Do not send them through this website.
Data retention: What is collected, who can access it, and when records are deleted.
Updates and incidents: Who handles updates, responds to incidents, and owns any unfinished work.