Security
The test is scoped.
The test reads the live grant, setting, secret, or exposure. The kill waits until that test has proved the risk. You can roll it back. The log stays.
Scoped access
You approve the connection. The test stays inside that scope.
A test you can read
The result names the object, the system, and why it is proven.
A kill you can reverse
Revoke, rotate, restrict, or block. Rollback stays available.
A log
Every test and every kill is written down. That is the proof.
Will a test break something?
The model runs a scoped live test. The kill waits until the test has proved the risk. You can roll it back. The log stays.
What access does the connection get?
The access you approve. An admin consent, a read-scoped key, or a role that includes only the kill actions you allow.
Is this a pentest?
No. Saasment tests a grant, setting, secret, permission, or exposure in place. It does not run an exploit chain or a ransomware simulation.
Who can see the log?
You can. The log is the proof you hand a customer. Saasment does not publish it.