Послуги з імітації атак хакерів для вдосконалення процесів кібербезпеки.

Послуги з імітації атак хакерів для вдосконалення процесів кібербезпеки.

Simulated hacker attacks to improve cyber security processes.

Simulated hacker attacks to improve cyber security processes.

/ BLOG

Testing Systems with Integrated AI Agents According to the OWASP Top 10

Heading photo

Companies are increasingly actively embedding LLMs into their products. AI agents already work at different points of interaction with the user, from chat assistants, CRM, and financial services to internal search, support, analytics, and automation.

For users, this is a convenient tool. For business, it is a way to accelerate processes. But from the point of view of cybersecurity, an AI agent is not just a new product feature. It is a separate attack surface.

The risk increases when the model not only answers requests, but also has access to APIs, databases, files, internal services, or business processes. In such an architecture, the LLM becomes an intermediary between the user and critical system functions.

If an attacker changes the model’s behavior through a specially formulated request, they can influence not only the response in the chat but also real actions in the system.

Why is classic web pentesting not enough?

Classic penetration testing of web applications checks the technical resilience of a product: authorization, authentication, API logic, the possibility of performing injections, business logic, correct configurations, and the processing of data entered by the user.
But LLM solutions have other classes of risks. Here it is important to assess how the model behaves: whether it is resistant to prompt injections, whether it protects the service context, what rights the AI agent has and how other system components use LLM responses.
For example, a classic web pentest can detect weak points in the API or access control. But it does not always show whether an attacker can, through a request, force the model to disclose the service context, activate a dangerous tool or pass an incorrect response further into the system.

Why is the OWASP Top 10 for LLM important for business?

OWASP Top 10 for LLM Applications covers ten main classes of risks for LLM solutions:

    Prompt Injection;

    Sensitive Information Disclosure;

    Supply Chain;

    Data and Model Poisoning;

    Improper Output Handling;

    Excessive Agency;

    System Prompt Leakage;

    Vector and Embedding Weaknesses;

    Misinformation;

    Unbounded Consumption.

For business, this is not a formal list of vulnerabilities, but a practical guideline. It shows where exactly the AI component can create risk: in user requests, access to data, work with external sources, connected tools, or processing of model responses.
One of the main risks is Prompt Injection. An attacker integrates instructions into the request that the model considers reliable and executes them. As a result, the agent can bypass restrictions, disclose sensitive information, or perform an action that the developers did not anticipate.
Another critical risk is Excessive Agency, that is, excessive autonomy of the agent. It occurs when the AI component has more rights than needed for a specific task.
If such an agent is connected to financial operations, CRM, billing or internal APIs, an error in the agent’s configurations is no longer limited to an incorrect response. It can affect confidential data, financial losses, business reputation and customer trust or the operation of the entire service.

What does penetration testing for LLM products include?

When an LLM is integrated into a product, it is necessary to test not only the external shell. It is important to check how the request passes through the application, model, internal services, and third-party integrations.
Specialists analyze:

    how the request to the model is formed;

    what data gets into the context;

    what tools are available to the agent;

    how the system limits its rights and checks the response;

    what actions it performs after receiving it.

Scenarios in which the model has access to confidential data require separate attention. This refers to the risk of Sensitive Information Disclosure from OWASP Top 10 for LLM Applications. In such cases, the model can accidentally disclose personal data, financial information, commercial information or other sensitive data.
For the company, this is not only a technical problem. If this risk is not controlled, the company can lose customer trust, violate internal security rules, and face issues during an audit or regulatory inspection.
Penetration testing of LLM solution integration assesses not only the vulnerability but also its impact on business processes, customer data and the company’s reputation.
Testing also covers scenarios where the LLM response is automatically passed to other system components. For example, the model generates an SQL query, command, workflow decision, or API instruction. If the output is not checked, the model’s response can turn into a really dangerous action.

What risks arise for companies?

The main risk is loss of control over the agent’s actions. If the AI component can create requests, change data, work with files, launch processes, or transfer information to external systems, its compromise can have negative business consequences.
For fintech, e-commerce, banking services, and SaaS products, this is especially critical. An incorrectly configured agent can disclose customers’ personal data, act without proper authorization, bypass business rules, or transfer information about the internal infrastructure to an attacker.
If the system does not control and limit the model’s output data, the LLM response can lead to a really dangerous action: data leakage, unauthorized operation, service failure or violation of security requirements.
In the worst-case scenario, this can end in complete system compromise:

    remote code execution;

    access to critical data;

    financial and reputational losses;

    fines from regulators;

    risk of compromising partners through integrated services or APIs.

A separate aspect is audit and compliance checking.
An AI agent is subject to audit if it works with corporate or customer data, has access to internal systems or can perform actions in business processes.
To assess the agent’s security, it is not enough to describe its general role. The customer must provide the auditor with information about the agent’s role, data sources, access levels, connected systems, permitted actions, established restrictions, logging and the results of testing risk scenarios.
Without this, it is more difficult to confirm that the company controls risks related to data, access and autonomous actions of the LLM.

Where to start the check?

The first step is to describe the architecture of the AI component. It is necessary to determine where the LLM is used, what data sources it sees, the tools that can be called, the roles of users who interact with the agent, and the actions performed by the system automatically.
The second step is to check the agent’s rights. Often, the AI component receives excessive access “for development convenience.” At the launch stage, this seems like a quick solution, but in a production environment, it creates unnecessary risk. The agent must have only those permissions that are needed for a specific scenario.
The third step is to contact specialists who conduct penetration testing of LLM solutions according to OWASP Top 10 for LLM Applications. They check not only the web interface and API, but also specific risks for systems with integrated AI: prompt injection, leakage of sensitive data, context isolation, connected APIs, processing of the model’s response and restrictions on the agent’s autonomous actions.
Logging settings should also be checked separately. The security team must see what requests the agent receives, what tools it calls, what decisions the system makes and what actions are performed after the model’s response. Without this, incident investigation can become almost impossible.

Ignoring risks costs more than testing

AI agents have already become part of the business logic of many products. Along with this, they have brought new classes of risks that are not covered by standard web application pentesting.
Companies need to separately check the model’s behavior, its context, accesses, connected tools and abuse scenarios. This is not only a matter of technical security. It is the protection of customer data, finances, reputation, partner relationships, and audit readiness.
IT Specialist conducts penetration testing of systems with integrated LLMs and AI agents, considering the OWASP Top 10 for LLM, the product’s business logic and real cyberattack scenarios.
Our team analyzes potential attack vectors, checks the AI agent’s access rights, tests risky scenarios and detects weak points before attackers use them.
Based on the results of the check, you will receive a report with a list of identified vulnerabilities and clear recommendations for eliminating them and improving the security level of your system.
IT Specialist pentesting helps assess the real state of your company’s protection and prepare the system for potential attacks.

Need expert advice?