AI agents are entering procurement, subsurface analysis and operational planning. Their access can span supplier contracts, well data and engineering tools. Oktsec helps you test that access and control the actions your agents are allowed to take.
YPF and Globant announced a program of 46 agents for supply-chain workflows.See the industry evidence
Published projects already cover purchasing, technical interpretation and specialist software. Each introduces a different question about data access and decision authority.
Digital Suppl.AI targets procurement, inventory, contracts and suppliers. The announcement describes agents to be developed; it does not establish that all 46 are live.
Read the project announcementENERGYai’s 90-day trial covered seismic interpretation and reservoir insights. ADNOC reported using data from more than 15% of its onshore and offshore wells.
Read the trial resultsSLB launched Tela for workflows including well-log interpretation, drilling analysis and equipment performance. Its framework also supports customer-built and partner-developed agents.
Read the product announcementA purchasing agent may read commercial terms. A technical agent may use proprietary well data. If it can also call tools, the review must cover what it can change, which destinations it can reach and who authorized the action. That is the security scope to establish before expanding a deployment.
Public accounts reviewed September 9, 2026. These organizations are not presented as Oktsec customers. Security implications are Oktsec’s analysis, not reported incidents at these companies.
For operators and service companies in Vaca Muerta, the first boundary may be a supplier portal, an inventory system or a technical repository. Review the point where an agent can move from gathering information to changing a record or sharing it with another company.
Compare quotes and stock availability while keeping supplier changes and purchasing approval under separate permissions.
At stake: commercial terms and purchasing authorityUse equipment history to draft a work order. Keep closing an order and releasing equipment in the existing approval process.
At stake: the integrity of maintenance recordsLimit the agent to the assigned asset and approved recipients. Test whether a contractor document can trigger access to unrelated well data.
At stake: proprietary data shared across companiesAI can reduce the effort of reviewing technical reports, comparing suppliers and preparing work. Teams need to know which data an agent can use, which actions it can take and which decisions still require approval.
Plan a secure rolloutBring together approved reports, asset records and supplier documents. Limit access to the assets and commercial information the task needs.
Let agents prepare comparisons and draft orders. Keep supplier changes, purchasing commitments and equipment release under the existing approval process.
Connect the assigned policy with available action records. Give the workflow owner a way to understand what was allowed, rejected or left outside coverage.
The taskCompare three quotes for replacement pump parts and prepare a recommendation.
Allow document retrieval and draft creation for this request.
The buyer receives a comparison to review.Price, availability and the selected supplier remain subject to the buyer’s review.Exclude purchase submission and vendor updates from this agent’s tool permissions.
The routed purchase call is denied.Test alternate tools and backend credentials too. Denying one tool is not enough if another path can submit the order.Illustrative configuration to validate in an assessment. Backend permissions and alternate access paths must be tested alongside the supported Oktsec integration.
Use representative quotes and contractor reports to test instruction injection, excessive permissions and alternate routes.
Explore AssessmentAt supported Node integrations, limit tools and parameters. Review assigned policy and available action evidence in Cloud.
Explore Control + CloudReview MCP servers, skills and dependencies used by the agent. Continuous monitoring of external ecosystem changes is in development.
Explore SignalCoverage follows the configured integration. Industrial control and safety systems remain under their dedicated protections. Review backend permissions, bypass paths and site connectivity before deployment.
Check deployment coverageBring the workflow owner and security team. Agree the data, connected tools and decisions that must stay with an authorized person.
The agent completes the comparison or draft it is assigned. Attempts to change supplier records, submit a purchase or export unrelated data are tested against the agreed permissions.
Reproducible findings, prioritized access and integration changes, and a record of what was tested. Use the findings to define a Control evaluation and agree any retesting.
Plan an assessmentIdentify the task, its owner, the connected systems and the permitted actions. Test that the intended workflow works, that out-of-scope actions are rejected on the configured path, and that alternate access routes and evidence gaps are documented.
Oktsec secures configured AI agent communication and tool paths. It does not replace industrial network monitoring, PLC protection or safety instrumented systems. Direct process control is outside this proposed assessment scope.
Start with one operator or service-company workflow, such as maintenance preparation or contractor document review. Identify its owner, connected tools, permitted data and approval steps. Agree the test environment and delivery arrangements before testing.
Coverage depends on the actual integration. Review the API, MCP server or other supported path, backend permissions and alternate access routes before claiming enforcement. This page does not imply a prebuilt connector to your platform.