Skip to content

Commit 19b3a48

Browse files
authored
Merge pull request #1931 from DebLanger/US317434_CAPs
new caps rules
2 parents 6b43ccf + 21a0fd8 commit 19b3a48

File tree

2 files changed

+20
-1
lines changed

2 files changed

+20
-1
lines changed

exposure-management/predefined-classification-rules-and-levels.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,4 +113,8 @@ Current asset types are:
113113
| Immutable Azure Storage | Cloud resource | Medium | This rule applies to Azure storage accounts that have immutability support enabled. Immutability stores business data in a write once read many (WORM) state, and usually indicates that the storage account holds critical or sensitive data that must be protected from modification. |
114114
| Immutable and Locked Azure Storage | Cloud resource | High | This rule applies to Azure storage accounts that have immutability support enabled with a locked policy. Immutability stores business data in a write once read many (WORM). Data protection is increased with a locked policy to ensure that data can’t be deleted or its retention time shortened. These settings usually indicate that the storage account holds critical or sensitive data that must be protected from modification or deletion. Data might also need to align with compliance policies for data protection. |
115115
| Azure Virtual Machine with a Critical User Signed In | Cloud resource | High | This rule applies to virtual machines protected by Defender for Endpoint, where a user with a high or very high criticality level is signed in. The signed-in user can be through a joined or registered device, an active browser session, or other means. |
116-
| Key Vaults with Many Connected Identities | Cloud resource | High | This rule identifies Key Vaults that can be accessed by a large number of identities, compared to other Key Vaults. This often indicates that the Key Vault is used by critical workloads, such as production services. |
116+
| Azure Key Vaults with Many Connected Identities | Cloud resource | High | This rule identifies Key Vaults that can be accessed by a large number of identities, compared to other Key Vaults. This often indicates that the Key Vault is used by critical workloads, such as production services. |
117+
| Locked Azure Kubernetes Service cluster | Cloud resource | Low | This is an Azure Kubernetes Service cluster that is safeguarded by a lock. Locks are used to protect assets from deletion and modifications. Usually, administrators use locks to safeguard critical cloud assets in their environment, and to protect them from accidental deletion and unauthorized modifications. |
118+
| Premium tier Azure Kubernetes Service cluster | Cloud resource | High | This rule applies to Azure Kubernetes Service clusters with premium tier cluster management. Premium tiers are recommended for running production or mission-critical workloads that need high availability and reliability. |
119+
| Azure Kubernetes Service cluster with multiple nodes | Cloud resource | High | This rule applies to Azure Kubernetes Service clusters with a large number of nodes. This often indicates that the cluster is used for critical workloads, such as production workloads. |
120+
| Azure Arc Kubernetes cluster with multiple nodes | Cloud Resource | High | This rule applies to Azure Arc Kubernetes clusters with a large number of nodes. This often indicates that the cluster is used for critical workloads, such as production workloads. |

exposure-management/whats-new.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,19 @@ Learn more about MSEM by reading the blogs, [here](https://techcommunity.microso
2626
2727
## December 2024
2828

29+
### New predefined classifications
30+
31+
The following predefined classification rules were added to the critical assets list:
32+
33+
| Classification | Description |
34+
| :--------------------------------------------------- | :----------------------------------------------------------- |
35+
| Locked Azure Kubernetes Service cluster | This rule applies to Azure Kubernetes Service clusters that are safeguarded by a lock. |
36+
| Premium tier Azure Kubernetes Service cluster | This rule applies to premium tier Azure Kubernetes Service clusters. |
37+
| Azure Kubernetes Service cluster with multiple nodes | This rule applies to Azure Kubernetes Service clusters with multiple nodes. |
38+
| Azure Arc Kubernetes cluster with multiple nodes | This rule applies to Azure Arc clusters with multiple nodes. |
39+
40+
For more information, see, [Predefined classifications](predefined-classification-rules-and-levels.md)
41+
2942
### New documentation library for Microsoft's unified security operations platform
3043

3144
Find centralized documentation about [Microsoft's unified SecOps platform in the Microsoft Defender portal](/unified-secops-platform/overview-unified-security). Microsoft's unified SecOps platform brings together the full capabilities of Microsoft Sentinel, Microsoft Defender XDR, Microsoft Security Exposure Management, and generative AI into the Defender portal. Learn about the features and functionality available with Microsoft's unified SecOps platform, then start to plan your deployment.
@@ -138,6 +151,8 @@ The following predefined classification rule was added to the critical assets li
138151
| ------------------------------------------------------------ | ------------------------------------------------------------ |
139152
| **Hyper-V Server** | This rule applies to devices identified as Hyper-V servers within a domain. These servers are essential for running and managing virtual machines within your infrastructure, serving as the core platform for their creation and management. |
140153

154+
For more information, see, [Predefined classifications](predefined-classification-rules-and-levels.md)
155+
141156
### Enhanced visibility for scoped users
142157

143158
This change now allows users who have been granted access to only some of the organization's devices to see the list of affected assets in metrics, recommendations, events, and initiative history within their specific scope.

0 commit comments

Comments
 (0)