Skip to content

Commit 0d20f7b

Browse files
committed
Acrolinx fixes
1 parent 4178acf commit 0d20f7b

File tree

2 files changed

+13
-9
lines changed

2 files changed

+13
-9
lines changed

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,4 +57,8 @@ 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. 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**.
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**.
61+
62+
## Related articles
63+
64+
- [Learn more about Microsoft Secure Score](/defender-xdr/microsoft-secure-score)

ATPDocs/remove-inactive-service-account.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,15 @@ ms.topic: how-to
77

88
# Security Assessment: Remove Inactive Service Accounts
99

10-
This recommendation lists Active Directory service accounts that have been detected as inactive (stale) within the past 180 days.
10+
This recommendation lists Active Directory service accounts detected as inactive (stale) within the past 180 days.
1111

1212
## Why do inactive service accounts pose a risk?
1313

14-
Unused service accounts can pose significant security risks to your organization, as some of these accounts can possess elevated privileges, which, if accessed by an attacker, could result in substantial damage. Therefore, it is imperative to identify and address any unused or orphaned service accounts.
14+
Unused service accounts can pose significant security risks to your organization, as some of these accounts can possess elevated privileges, which, if accessed by an attacker, could result in substantial damage. Therefore, it's imperative to identify and address any unused or orphaned service accounts.
1515

1616
## How do I use this security assessment to improve my organizational security posture?
1717

18-
To leverage this security assessment effectively, follow these steps:
18+
To use this security assessment effectively, follow these steps:
1919

2020
1. Review the recommended action at [https://security.microsoft.com/securescore?viewid=actions ](https://security.microsoft.com/securescore?viewid=actions ) for Remove inactive service account.
2121
1. Review the list of exposed entities to discover which of your service account is inactive.
@@ -24,15 +24,15 @@ To leverage this security assessment effectively, follow these steps:
2424

2525
1. Take appropriate actions on those entities by removing the service account. For example:
2626

27-
- Disable the account: Prevent any usage by disabling the account identified as exposed.
27+
- **Disable the account:** Prevent any usage by disabling the account identified as exposed.
2828

29-
- Monitor for impact: Wait several weeks and monitor for operational issues, such as service disruptions or errors.
29+
- **Monitor for impact:** Wait several weeks and monitor for operational issues, such as service disruptions or errors.
3030

31-
- Delete the account: If no issues are observed, proceed to delete the account and fully remove its access.
31+
- **Delete the account:** If no issues are observed, 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 might take time until it's marked as **Completed**.
3535
3636
## Related articles
3737

38-
- [Microsoft Secure Score](/defender-xdr/microsoft-secure-score)
38+
- [Learn more about Microsoft Secure Score](/defender-xdr/microsoft-secure-score)

0 commit comments

Comments
 (0)