> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/cloud-penetration-testing-tool-activity.md).
# Cloud penetration testing tool activity
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 7 Days |
| Required Data | Requires one of the following data sources:
AWS Audit Log OR Azure Audit Log OR Gcp Audit Log OR Microsoft Graph Logs
|
| Detection Modules | Cloud |
| Detector Tags | Microsoft Graph Activity Logs |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | User Execution (T1204) |
| Severity | High |
### Description
A cloud API was successfully executed using a known cloud penetration testing tool.
### Attacker's Goals
Leverage known attack tools to enumerate resources, identify vulnerabilities, or exploit cloud configurations.
### Investigative actions
* Confirm if authorized penetration testing activity is currently scheduled.
* Review the API operations performed by the identity to determine the intent and scope of the activity.
### Variations
Cloud penetration testing tool usage attempt
**Synopsis**
| Field | Value |
| ----------------- | ---------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | User Execution (T1204) |
| Severity | Informational |
**Description**
A failed cloud API was executed using a known cloud penetration testing tool.
**Attacker's Goals**
Leverage known attack tools to enumerate resources, identify vulnerabilities, or exploit cloud configurations.
**Investigative actions**
* Confirm if authorized penetration testing activity is currently scheduled.
* Review the API operations performed by the identity to determine the intent and scope of the activity.
Cloud security assessment tool activity
**Synopsis**
| Field | Value |
| ----------------- | ---------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | User Execution (T1204) |
| Severity | Low |
**Description**
A cloud API was successfully executed using a known cloud security assessment tool.
**Attacker's Goals**
Leverage known attack tools to enumerate resources, identify vulnerabilities, or exploit cloud configurations.
**Investigative actions**
* Confirm if authorized penetration testing activity is currently scheduled.
* Review the API operations performed by the identity to determine the intent and scope of the activity.
Cloud penetration testing tool activity by Azure application
**Synopsis**
| Field | Value |
| ----------------- | ---------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | User Execution (T1204) |
| Severity | Informational |
**Description**
A cloud API was successfully executed using a known cloud penetration testing tool by an Azure application.
**Attacker's Goals**
Leverage known attack tools to enumerate resources, identify vulnerabilities, or exploit cloud configurations.
**Investigative actions**
* Confirm if authorized penetration testing activity is currently scheduled.
* Review the API operations performed by the identity to determine the intent and scope of the activity.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/cloud-penetration-testing-tool-activity.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.