FinSAFE Product details
Set clear boundaries for agent work
FinSAFE lets teams define what an agent may change, what it may read or write, and where its data may go.
Machine security
An agent that can edit files, install dependencies or troubleshoot a machine may also reach system administration interfaces. FinSAFE separates routine agent work from protected system operations.
| Risk area | What can go wrong | Control described in the Windows reference |
|---|---|---|
| Permissions and ownership | Files or programs become inaccessible, or access is widened | Check changes to object permissions and ownership |
| Registry and startup settings | Programs fail or Windows may not start | Check access to registry, protected files and system management interfaces |
| Processes and services | Critical programs crash or services stop | Check process handles and service permissions |
| Accounts, tasks and startup items | A privileged account or persistent launch path is left behind | Check account, scheduled-task and startup interfaces |
| Network and security settings | Connections fail or protections are weakened | Check access to network and security settings |
| Raw disk writes | Partitions or file systems are damaged | Check permissions for raw-device write handles |
The controls are intended to restrict unauthorized operations by a protected agent. They do not replace endpoint security or administrator policy.
Keep resource use bounded
FinSAFE can limit memory and the number of child processes used by an agent and its tools. Where the execution path supports it, a task can also be stopped after a time limit, with its process tree cleaned up.
Data security
Teams define which files an agent can access and which network destinations it can reach.
| Example location | Access | Example operations |
|---|---|---|
D:\Work\Projects |
Read and write | Create, read, edit, delete, rename and move |
D:\Reference |
Read only | List, read and search |
D:\Private |
Denied | No listing, reading or writing |
Govern data sent outside the machine
- Network targets: allow the model and business services the task needs; reject destinations outside the configured policy.
- Inspectable HTTPS requests: when TLS inspection is enabled and the request is supported, check configured categories of personally identifiable information (PII).
- Policy response: record an alert and continue, block the request, or pause for approval of that request. A cancelled or timed-out approval does not send it.
- Records: retain requests, responses, alerts and approval results according to configuration. The Windows reference describes encrypted local storage using AES-GCM with a key protected by Windows DPAPI.
Inspection depends on the request path and the configured policy. It should not be described as inspection of every encrypted connection.
Next step
Let agents act without letting them loose
Talk with a Forward Deployed Engineer about FinSAFE on its own or as part of FinAI OS.