Monitoring that does not become a hole in your perimeter
The check service itself visits addresses that users provide. That is why every target, redirect and response is treated as untrusted data.
Protection against internal requests
Private, local, service and reserved address ranges are blocked before the connection, including in browser checks.
Pinned DNS
The address is validated again before the request and after every redirect, and the connection is pinned to the validated IP.
Encrypted secrets
Passwords, tokens and keys are encrypted with AES-256-GCM, are not shown after saving and are masked in stored requests.
Customer isolation
Business and organization boundaries apply in permissions, services and query filters, and are verified by tests.
Read-only in databases
Queries and commands to databases are checked on save, and anything that changes data is rejected.
Audit log
Every settings change is saved with its author, time and the difference in values.
Internal services have a separate path
A private agent runs checks inside your network and connects outbound only. The cloud network policy for other monitors is not relaxed, and you limit the addresses the agent can reach.
- Outbound connections only
- The token is stored as a hash and revoked in one click
- Secrets are filled in before the task is sent
- Allowed networks are set on the agent side
Access and data
Sign-in via A3.ID
The A3 ecosystem account and payment. The product key never reaches the browser: the server performs the token exchange.
Roles and granular permissions
Five roles and granular permissions, product access by department.
Export and closure
The owner can export business data and close the account from the settings.
Shall we discuss your monitoring setup?
Tell us which products, networks and channels you need to connect. We will help you break services down into products and resources and set up the first checks.