Netarx exists to stop social engineering, deepfake and impersonation attacks. NIK Agent takes that posture and points it at the AI assistant your team is going to use anyway, so the assistant cannot become the next way in.
The frontier labs run your prompts through infrastructure you do not control, on terms you cannot audit. NIK Agent is built the other way around.
NIK Agent is not a chatbot with a login screen bolted on. The Netarx Identity Key is part of how it decides what to do and who to trust.
The identity layer is the same one Netarx runs on. How NIK works
A known person on an authenticated device. Act as normal.
A new contact, or signals worth a second look. Confirm out of band before you act.
The models found a fake voice, face, message or image. Stop.
An assistant that cannot show its work cannot be trusted with a wire, a contract or a customer. NIK Agent shows its reasoning as it goes and keeps the trace.
The attacks that work against assistants are the same attacks Netarx has been detecting for years: a trusted voice, a false urgency, an instruction from someone who is not who they say they are.
A message that claims to come from your boss is checked against your real relationships and communication patterns before the agent acts on it.
Instructions hidden inside a document are treated as content to report, not as orders to follow, and the attempt is visible in the trace.
A cloned voice or a face-swapped video that reaches the agent gets the same treatment it gets everywhere else in NIK: amber or red, with the reason.
Payment details, new recipients and outbound sends get a second look, and administrators decide how much autonomy the agent is allowed.
A security page is only useful if it is accurate, so here is the boundary.
We would rather answer hard questions before the rollout than after it. Ask for the security review pack and the deployment plan.