Skip to content

Commit 4178acf

Browse files
committed
add related articles
1 parent e897646 commit 4178acf

File tree

2 files changed

+10
-6
lines changed

2 files changed

+10
-6
lines changed

ATPDocs/remove-discoverable-passwords-active-directory-account-attributes.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ Certain free-text attributes are often overlooked during hardening but are reada
1414

1515
Attackers seek low-friction paths to expand access. Exposed passwords in these attributes represent an easy win because:
1616

17-
- The attributes are not access-restricted.
17+
- The attributes aren't access-restricted.
1818

19-
- They are not monitored by default.
19+
- They aren't monitored by default.
2020

2121
- They provide context attackers can exploit for lateral movement and privilege escalation.
2222

@@ -29,7 +29,7 @@ Removing exposed credentials from these attributes reduces the risk of identity
2929
> This security recommendation is part of Microsoft Defender for Identity and is powered by AI-based analysis of free-text attributes in Active Directory.
3030
> Findings can include false positives. Always validate the results before taking action.
3131
32-
Microsoft Defender for Identity detects potential credential exposure in Active Directory by analyzing commonly used free-text attributes. This includes looking for common password formats, hints, `'description'`, `'info'`, and `'adminComment'` fields, as well as other contextual clues that may suggest the presence of credential misuse. Microsoft Defender for Identity detects indicators such as:
32+
Microsoft Defender for Identity detects potential credential exposure in Active Directory by analyzing commonly used free-text attributes. This includes looking for common password formats, hints, `'description'`, `'info'`, and `'adminComment'` fields, and other contextual clues that might suggest the presence of credential misuse. Microsoft Defender for Identity detects indicators such as:
3333

3434
- Plaintext passwords or variations. For example, '`Password=Summer2024!'`
3535

@@ -44,7 +44,7 @@ Detected matches are surfaced in **Secure Score** and the **Security Assessment
4444

4545
To address this security assessment, follow these steps:
4646

47-
1. Review the recommended action at[https://security.microsoft.com/securescore?viewid=actions](https://security.microsoft.com/securescore?viewid=actions) forRemove discoverable passwords in Active Directory account attributes.
47+
1. Review the recommended action at [https://security.microsoft.com/securescore?viewid=actions](https://security.microsoft.com/securescore?viewid=actions) for Remove discoverable passwords in Active Directory account attributes.
4848
1. Review the exposed entries in the security report. Identify any field content that includes:
4949

5050
- Cleartext passwords
@@ -57,4 +57,4 @@ To address this security assessment, follow these steps:
5757
1. Fully remove the sensitive information. Don’t just mask the value. Partial obfuscation (for example, P@ssw***) can still offer useful clues to attackers.
5858

5959
> [!NOTE]
60-
> Assessments are updated in near real time, and scores and statuses are updated every 24 hours. The list of impacted entities is updated within a few minutes of your implementing the recommendations. The status might take time until it's marked as **Completed**.
60+
> Assessments are updated in near real time. Scores and statuses are updated every 24 hours. The list of impacted entities is updated within a few minutes of you implementing the recommendations. The status might take time until it's marked as **Completed**.

ATPDocs/remove-inactive-service-account.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,4 +31,8 @@ To leverage this security assessment effectively, follow these steps:
3131
- Delete the account: If no issues are observed, proceed to delete the account and fully remove its access.
3232

3333
> [!NOTE]
34-
> Assessments are updated in near real time, and scores and statuses are updated every 24 hours. The list of impacted entities is updated within a few minutes of your implementing the recommendations. The status may take time until it's marked as **Completed**.
34+
> Assessments are updated in near real time, and scores and statuses are updated every 24 hours. The list of impacted entities is updated within a few minutes of your implementing the recommendations. The status may take time until it's marked as **Completed**.
35+
36+
## Related articles
37+
38+
- [Microsoft Secure Score](/defender-xdr/microsoft-secure-score)

0 commit comments

Comments
 (0)