AWS Security ChangesHomeSearch

AWS securityhub documentation change

Service: securityhub · 2025-06-19 · Documentation low

File: securityhub/latest/userguide/account-management-manual.md

Summary

Updated documentation to reflect product name changes from 'Security Hub' to 'Security Hub CSPM' across multiple sections, including titles, descriptions, and links. Added CSPM references to clarify Cloud Security Posture Management context in account management processes.

Security assessment

The changes are primarily branding/nomenclature updates (adding CSPM references) rather than addressing security vulnerabilities or introducing new security features. No evidence of patching vulnerabilities or responding to security incidents. The updates maintain existing security documentation but don't add new security guidance.

Diff

diff --git a/securityhub/latest/userguide/account-management-manual.md b/securityhub/latest/userguide/account-management-manual.md
index 263f36eed..d49da2a2a 100644
--- a//securityhub/latest/userguide/account-management-manual.md
+++ b//securityhub/latest/userguide/account-management-manual.md
@@ -3 +3 @@
-[Documentation](/index.html)[AWS Security Hub](/securityhub/index.html)[User Guide](what-is-securityhub.html)
+[Documentation](/index.html)[AWS Security Hub](/securityhub/index.html)[ User Guide ](what-is-security-hub-adv.html)
@@ -5 +5 @@
-# Managing accounts by invitation in Security Hub
+# Managing accounts by invitation in Security Hub CSPM
@@ -7 +7 @@
-You can centrally manage multiple AWS Security Hub accounts in two ways, by integrating Security Hub with AWS Organizations or by manually sending and accepting membership invitations. You must use the manual process if you have a standalone account or you don't integrate with AWS Organizations. In manual account management, the Security Hub administrator invites accounts to become members. The administrator-member relationship is established when a prospective member accepts the invitation. A Security Hub administrator account can manage Security Hub for up 1,000 invitation-based member accounts. 
+You can centrally manage multiple AWS Security Hub Cloud Security Posture Management (CSPM) accounts in two ways, by integrating Security Hub CSPM with AWS Organizations or by manually sending and accepting membership invitations. You must use the manual process if you have a standalone account or you don't integrate with AWS Organizations. In manual account management, the Security Hub CSPM administrator invites accounts to become members. The administrator-member relationship is established when a prospective member accepts the invitation. A Security Hub CSPM administrator account can manage Security Hub CSPM for up 1,000 invitation-based member accounts. 
@@ -11 +11 @@ You can centrally manage multiple AWS Security Hub accounts in two ways, by inte
-If you create an invitation-based organization in Security Hub, you can subsequently [transition to using AWS Organizations](./accounts-transition-to-orgs.html) instead. If you have more than one member account, we recommend using AWS Organizations instead of Security Hub invitations to manage your member accounts. For information, see [Managing Security Hub administrator and member accounts with Organizations](./securityhub-accounts-orgs.html).
+If you create an invitation-based organization in Security Hub CSPM, you can subsequently [transition to using AWS Organizations](./accounts-transition-to-orgs.html) instead. If you have more than one member account, we recommend using AWS Organizations instead of Security Hub CSPM invitations to manage your member accounts. For information, see [Managing Security Hub CSPM for multiple accounts with AWS Organizations](./securityhub-accounts-orgs.html).
@@ -13 +13 @@ If you create an invitation-based organization in Security Hub, you can subseque
-Cross-Region aggregation of findings and other data is available for accounts that you invite through the manual invitation process. However, the administrator must invite the member account from the aggregation Region and all linked Regions in order for cross-Region aggregation to work. In addition, the member account must have Security Hub enabled in the aggregation Region and all linked Regions to give the administrator the ability to view findings from the member account.
+Cross-Region aggregation of findings and other data is available for accounts that you invite through the manual invitation process. However, the administrator must invite the member account from the aggregation Region and all linked Regions in order for cross-Region aggregation to work. In addition, the member account must have Security Hub CSPM enabled in the aggregation Region and all linked Regions to give the administrator the ability to view findings from the member account.
@@ -15 +15 @@ Cross-Region aggregation of findings and other data is available for accounts th
-Configuration policies aren't supported for manually-invited member accounts. Instead, you must configure Security Hub settings separately in each member account and AWS Region when you use the manual invitation process.
+Configuration policies aren't supported for manually-invited member accounts. Instead, you must configure Security Hub CSPM settings separately in each member account and AWS Region when you use the manual invitation process.
@@ -17 +17 @@ Configuration policies aren't supported for manually-invited member accounts. In
-You must also use the manual invitation-based process for accounts that don't belong to your organization. For example, you might not include a test account in your organization. Or, you might want to consolidate accounts from multiple organizations under a single Security Hub administrator account. The Security Hub administrator account must send invitations to accounts that belong to other organizations.
+You must also use the manual invitation-based process for accounts that don't belong to your organization. For example, you might not include a test account in your organization. Or, you might want to consolidate accounts from multiple organizations under a single Security Hub CSPM administrator account. The Security Hub CSPM administrator account must send invitations to accounts that belong to other organizations.
@@ -19 +19 @@ You must also use the manual invitation-based process for accounts that don't be
-On the **Configuration** page of the Security Hub console, accounts that were added by invitation are listed in the **Invitation accounts** tab. If you use [central configuration](./central-configuration-intro.html), but also invite accounts outside of your organization, you can view findings from invitation-based accounts in this tab. However, the Security Hub administrator can't configure invitation-based accounts across Regions through the use of configuration policies.
+On the **Configuration** page of the Security Hub CSPM console, accounts that were added by invitation are listed in the **Invitation accounts** tab. If you use [central configuration](./central-configuration-intro.html), but also invite accounts outside of your organization, you can view findings from invitation-based accounts in this tab. However, the Security Hub CSPM administrator can't configure invitation-based accounts across Regions through the use of configuration policies.
@@ -25 +25 @@ The topics in this section explain how to manage member accounts through invitat
-  * [Adding and inviting member accounts in Security Hub](./securityhub-accounts-add-invite.html)
+  * [Adding and inviting member accounts in Security Hub CSPM](./securityhub-accounts-add-invite.html)
@@ -27 +27 @@ The topics in this section explain how to manage member accounts through invitat
-  * [Responding to an invitation to be a Security Hub member account](./securityhub-invitation-respond.html)
+  * [Responding to an invitation to be a Security Hub CSPM member account](./securityhub-invitation-respond.html)
@@ -29 +29 @@ The topics in this section explain how to manage member accounts through invitat
-  * [Disassociating member accounts in Security Hub](./securityhub-disassociate-members.html)
+  * [Disassociating member accounts in Security Hub CSPM](./securityhub-disassociate-members.html)
@@ -31 +31 @@ The topics in this section explain how to manage member accounts through invitat
-  * [Deleting member accounts in Security Hub](./securityhub-delete-member-accounts.html)
+  * [Deleting member accounts in Security Hub CSPM](./securityhub-delete-member-accounts.html)
@@ -33 +33 @@ The topics in this section explain how to manage member accounts through invitat
-  * [Disassociating from a Security Hub administrator account](./securityhub-disassociate-from-admin.html)
+  * [Disassociating from a Security Hub CSPM administrator account](./securityhub-disassociate-from-admin.html)
@@ -35 +35 @@ The topics in this section explain how to manage member accounts through invitat
-  * [Transitioning to Organizations to manage accounts in Security Hub](./accounts-transition-to-orgs.html)
+  * [Transitioning to Organizations to manage accounts in Security Hub CSPM](./accounts-transition-to-orgs.html)
@@ -48 +48 @@ Disassociating organization member accounts
-Adding and inviting member accounts in Security Hub
+Adding and inviting member accounts