Defender for Cloud Alert JSON: Finding Privilege Escalation Tactic
Short answer
B Search the Defender for Cloud alert JSON intent key for PrivilegeEscalation to locate alerts using the Privilege Escalation MITRE ATT&CK tactic.
Question
You need to locate alerts that indicate the use of the Privilege Escalation MITRE ATT&CK tactic.
Which JSON key should you search?
Key Takeaways
The question tests whether you know the Defender for Cloud alert JSON contract for MITRE tactic data; the trap is assuming the tactic lives in the free-form extendedProperties bag rather than the dedicated intent field.
Microsoft Defender for Cloud exposes each alert's MITRE ATT&CK tactic in the top-level intent JSON property, so a third-party SIEM can filter on PrivilegeEscalation. This page explains why intent (B) is the correct search key and why description, entities, and extendedProperties are traps.
Common mistake: Choosing C (ExtendedProperies) because some alert payloads carry MITRE metadata in extended properties; that bag is product-specific and not the canonical top-level tactic field, so filtering on it gives inconsistent coverage.
Expert Analysis
The schema field, not prose. In the Defender for Cloud alerts REST payload, intent is the top-level alert property that carries the MITRE ATT&CK tactic label. The REST sample uses "intent": "Execution", and the same property can return PrivilegeEscalation for privilege escalation alerts. A third-party SIEM parsing the raw alert JSON should therefore look for the intent key and test for that string. That makes Option B the correct choice.
Why the other keys fail. Option A description is human-readable narrative; it may mention privilege escalation in wording, but it is not a controlled tactic field, so it is unsuitable for deterministic correlation. Option D entities describes the affected resources (accounts, hosts, files, and so on), not the adversary's goal. Option C extendedProperties is a product-specific bag; some alerts may carry MITRE metadata there, which is why reviewers split between C and B, but it is not the canonical top-level field for the alert's ATT&CK tactic in this schema. Searching C gives inconsistent coverage.
Adjacent decision that changes the answer. If the question were about Microsoft Sentinel's SecurityAlert table instead of the raw Defender for Cloud alert JSON, the tactic is exposed as the Tactics column, with Techniques alongside it, not as intent. Similarly, a Microsoft Graph security API consumer may see different property names. Identify the data contract—raw Defender for Cloud alert versus SIEM-normalized table—before choosing a key.
Operational consequence. A SIEM rule that searches description or entities will miss structured tactic matches; privilege escalation alerts will not route to the high-priority queue, increasing dwell time. A rule that searches extendedProperties may appear to work for a subset and then fail silently as alert types vary. Build the parser around intent, then optionally fall back to extendedProperties only after checking a specific alert type.
Official Reference
https://learn.microsoft.com/en-us/rest/api/defenderforcloud/alerts/list?tabs=HTTP#intent
This link opens the official vendor documentation in a new tab.
Exam Strategy
For alert-schema questions, identify the data contract before matching a field name: raw Defender for Cloud alert JSON, Sentinel's normalized SecurityAlert table, and Graph security alerts use different property names. Read the sample payload in the vendor REST reference and look for a value that is already a MITRE tactic (Execution, PrivilegeEscalation), which points to intent here. Treat free-text fields and entity lists as traps; they can contain matching words but are not controlled taxonomy fields. If two keys seem plausible, choose the one defined for that purpose by the schema.
Frequently Asked Questions
Which Defender for Cloud alert JSON key holds the MITRE ATT&CK tactic?
Can extendedProperties contain MITRE ATT&CK details in Defender for Cloud alerts?
How does the search change in Microsoft Sentinel?
Community Votes
66% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 19 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 19
-
VictorLiu 👍 21 Answered BB. Intent https://learn.microsoft.com/en-us/rest/api/defenderforcloud/alerts/list?tabs=HTTP#intent
-
Fcnet 👍 4Intent PrivilegeEscalation string Privilege escalation is the result of actions that allow an adversary to obtain a higher level of permissions on a system or network.
-
Fcnet 👍 4this is for the intent answer wich is the right answer
-
mimguy 👍 4On the exam July 7 2023
-
PhoenixSlasher 👍 3 Answered BB. Intent Personally find the extendedProperties to contain the data as well but Intent clearly defines Privilege Escalation without digging around in extended properties.
Show 14 more comments
-
Fcnet 👍 3https://learn.microsoft.com/en-us/rest/api/defenderforcloud/alerts/list?tabs=HTTP#intent
-
srajal 👍 3Which is correct answer
-
g_man_rap 👍 2Correct Answer: C. ExtendedProperties Explanation: The ExtendedProperties JSON key is designed to hold additional and structured information about the alert. In the context of Microsoft Defender for Cloud and other security platforms, this often includes detailed metadata such as MITRE ATT&CK tactic mappings. Therefore, searching the ExtendedProperties key will likely yield results that specifically indicate the Privilege Escalation tactic.
-
jayek 👍 2https://learn.microsoft.com/en-us/rest/api/defenderforcloud/alerts/list?tabs=HTTP#intent:~:text=%22High%22%2C-,%22intent%22%3A%20%22Execution%22%2C,-%22startTimeUtc%22%3A
-
WRITER00347 👍 2so C. ExtendedProperties
-
falkendarkness 👍 1Option B ("Intent") is not typically used to directly represent the MITRE ATT&CK tactics or techniques associated with an alert in Microsoft Defender for Cloud. The "Intent" field, if present in the alert data, might provide information about the suspected purpose or objective of the observed activity. However, it does not specifically indicate the MITRE ATT&CK tactic or technique being employed. On the other hand, the "ExtendedProperties" field often contains additional contextual information about the alert, including any associated MITRE ATT&CK tactics and techniques. This field is more likely to contain the specific details needed to identify alerts related to the Privilege Escalation tactic. Therefore, in the context of locating alerts related to the Privilege Escalation MITRE ATT&CK tactic, the "ExtendedProperties" field (Option C) is more relevant to search within the JSON data.
-
neo73 👍 1To locate Privilege Escalation MITRE ATT&CK tactic alerts in Microsoft Defender for Cloud, search the Description JSON key. To locate alerts that indicate the use of the Privilege Escalation MITRE ATT&CK tactic in Microsoft Defender for Cloud, you should search the Description JSON key. The Description key provides a detailed explanation or summary of the alert, and it may include information about the observed behavior or activity related to privilege escalation. By searching the Description key, you can filter and identify alerts that specifically mention or describe privilege escalation techniques. This can help in effectively reviewing and addressing such alerts using the third-party security information and event management (SIEM) solution.
-
WRITER00347 👍 1The JSON key you should search for to locate alerts that indicate the use of the Privilege Escalation MITRE ATT&CK tactic is extendedProperties. The extendedProperties key in the JSON structure of an alert contains the MITRE ATT&CK information for the alert, such as the tactics and techniques used by the attacker. The key contains the tactic name in the MITRE ATT&CK framework, such as "Privilege Escalation", "Initial Access", "Execution" and so on. You can use the extendedProperties key to filter and search for alerts that are related to the Privilege Escalation tactic in your third-party SIEM solution. It's also important to note that, the other options A,B,C are not related to the MITRE ATT&CK information and are used for different purposes.
-
mali1969 👍 1 Answered DThe JSON key that you should search for alerts that indicate the use of the Privilege Escalation MITRE ATT&CK tactic is Entities. This key contains information about the entities involved in the alert, such as users, devices, files, etc. The value of this key can include a MITRETechniques property that lists the MITRE ATT&CK techniques associated with the alert.
-
NICKTON81 👍 1 Answered BB. Intent https://learn.microsoft.com/en-us/rest/api/defenderforcloud/alerts/list?tabs=HTTP#intent:~:text=%22High%22%2C-,%22intent%22%3A%20%22Execution%22%2C,-%22startTimeUtc%22%3A
-
HAjouz 👍 1 Answered CWithin the JSON structure of a Microsoft Defender for Cloud alert, the MITRE ATT&CK tactic information is stored within the ExtendedProperties section.
-
neogeek87 👍 1 Answered BTested in Lab, Intent shows MITRE ATTACK & TACTIC information
-
chepeerick 👍 1B intent
-
JoshJosh 👍 1Entities
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SC-200 Questions
Access 80 questions with complete answers and detailed explanations.
View Full SC-200 Practice Test →