Secure and govern your AI agents. Assess risks, define permissions and approval rules, and keep a verifiable record of policy decisions.
Our founder joins the
Program Committee.
Oktsec joins NVIDIA’s
startup program.
Know what matters.
Act with context.
Security incidents, vulnerabilities and practical guidance to help your team decide what needs attention.
Explore RadarInstall OpenSSH 10.6p2 or the corrected distribution package, restart sshd and test a new connection. Preserve and review earlier logins, account changes and authorized keys on exposed systems.
Update Plex Media Server to 1.43.3.10861 or later and restrict remote access. Investigate previously exposed installations; updating alone does not remove a prior compromise.
Oktsec founder Gustavo Aragón received the award from Leandro Rizzuto, U.S. Ambassador to the Organization of American States (OAS), during ACE Barranquilla.
Read the award story15 letters of intent · 10 countriesExploring collaboration in cybersecurity, AI and training.
Evaluate a system, put controls around an AI pilot or help your team build the skills to move forward.
Test AI agents, web applications and APIs within an agreed scope. Get reproducible findings and recommended fixes.
A defined scope. Findings your engineers can use.
Scope an assessmentSet permissions, assign reviewers and define evaluation criteria for an AI workflow. Put these governance decisions into practice in a scoped pilot.
One workflow. Clear responsibilities and criteria.
Discuss a pilotTalks, workshops and training programs for companies, governments and universities. Work through AI risks and practical security decisions.
For technical teams and people getting started.
Explore trainingDefine who is responsible for an agent, what it can access and which actions need approval.
Test those controls and keep evidence your team can review.
Test one real agent workflow before production. Get reproducible findings, practical remediation and evidence your engineers can use.
Explore AssessmentApply explicit policy where agents act. Allow approved work, hold exceptions for review and keep a record of every decision.
Explore ControlReview the MCP servers, skills and packages entering your workflows. Understand their risks and review changes before updating an approval.
Explore SignalManage policies, exceptions and evidence across teams. Keep local enforcement close to the action and governance in one operating view.
Explore CloudChoose where to run Oktsec, connect controls to your governance requirements and explore workflows for your team.
Compare deployment options for your infrastructure and data requirements.
View deployment optionsSee how agent controls and audit evidence map to security and AI governance frameworks.
Explore the mappingsFind examples of agent workflows, the risks they introduce and the controls to apply.
Explore use cases14 min read
10 min read
8 min read
Explore Aguara and the open-source projects behind our work.
Open-source projectsHow requests are checked, where oktsec runs and how to verify the audit trail.
Explore deploymentAt the points between an agent and the tools or systems it can access. Depending on the workflow, that can be a local MCP proxy, a gateway or an HTTP service. Actions routed through oktsec are checked before they proceed.
No. The enforcement pipeline is deterministic. It evaluates identity, permissions and content against configured policy. A model does not decide whether an action is authorized.
You can keep your agent clients and MCP servers. Oktsec can wrap MCP server connections or sit in the request path as a gateway. The initial assessment identifies where the control belongs in your workflow.
Depending on the policy and severity, oktsec can flag and log the request, quarantine it for human review or block it. The audit record connects the request to the decision and the rules involved.
Review permissions when you add a tool or connector, change credentials or expand a task. Check the new access paths and test which actions can run without approval. A previous assessment covers the configuration tested at that time.
Yes. Audit records form a tamper-evident hash chain. When a node key is configured, records are also signed and can be verified offline with the public key.
Choose one workflow that touches code, tools, credentials or infrastructure. Define its scope, test the execution path and use the findings to decide where to apply control.
Pentesting, AI security and governance, and practical training. Work directly with our team to define the scope, priorities and next steps.