Easy ReviewDOP-C02
Configuration Management and IaC33

Security Hub

Collect CSPM findings, understand control prerequisites, and manage configuration and response across accounts and Regions.

Este conteúdo de estudo ainda não foi traduzido, então aparece em inglês. Ajude a traduzir

Security Hub CSPM consolidates security findings and evaluates resource settings against standards. Use account administration and Region aggregation to collect results, central configuration to apply settings, and automation with EventBridge to handle findings.

Findings, standards, and Config dependency

AWS Security Hub Cloud Security PostureThe security state of resources assessed against security requirements. Management (CSPM) collects security findingsA record of a security check or a security-related detection. and tests resource settings against security standardsA group of related security controls based on a security framework.. A finding is a record of a security check or detection. A controlA security requirement evaluated by one or more checks. is one security check requirement; a standard groups related controls. CSPM uses AWS Security Finding FormatThe common structure CSPM uses to represent findings from different providers. (ASFF), a shared structure for findings from different sources.

How it works

  1. Enable CSPM in the accounts and Regions that need coverage. The EnableSecurityHub API enables AWS Foundational Security Best Practices (FSBP) and CIS AWS Foundations Benchmark v1.2.0 by default. Set EnableDefaultStandards: false to opt out of those standards while keeping CSPM enabled.
  2. Enable the standards and controls you need. Supported frameworks include CIS, PCI DSS, and NIST, which define sets of security requirements. Most AWS control checks use service-linked Config rules, rules created for the service to evaluate resource settings.
  3. Provide the required resource recording. With CSPM alone, manually configure AWS Config in each participating account and Region. With both CSPM and Security Hub enabled, CSPM creates AWSConfigurationRecorderForSecurityHubCSPM automatically.
  4. Receive findings from integrations such as GuardDuty, Inspector, Macie, Firewall Manager, and IAM Access Analyzer. Patch Manager can also contribute patch compliance findings.

AWS added service-linked recorder guidance in May 2026. For older scenarios or CSPM-only setups, keep the manual Config prerequisite in mind. A configuration recorderAn AWS Config component that captures resource configuration data. is the component that captures resource settings.

Requirement Mechanism What it provides
Check AWS resource settings CSPM controls backed by service-linked Config rules Control findings
Collect findings from other security tools Product integrations Findings in a common format

Exam cues

  • If the question says assess resources against security standards and combine detector findings, think Security Hub CSPM, because it provides controls and a common findings view.
  • If the question says CSPM without Security Hub has missing control evaluations, think required Config recording, because most AWS controls need recorded resource settings.
  • If the question says collect integration findings without default standards, think EnableDefaultStandards: false, because CSPM can be enabled without automatically enabling those standards.

Remember

  • API default: EnableDefaultStandards is true.
  • API default standards: FSBP and CIS AWS Foundations Benchmark v1.2.0.
  • Manual recording: cover required resource types in every applicable account and Region.
  • Both services enabled: CSPM creates the service-linked recorder automatically.
  • Findings also arrive from supported third-party products.

Trap: CSPM alone needs manual Config recording for the required resource types. The automatic service-linked recorder applies when both CSPM and Security Hub are enabled.

Config rule results imported as CSPM findings
12AWS Configmanaged and custom rulesEventBridgerule evaluationsSecurity Hub CSPMASFF findings
  1. AWS Config publishes rule evaluations after CSPM enablement.

  2. The active Config integration converts evaluations to ASFF findings; CSPM control checks use a separate service-linked rule path.

Da documentação da AWS (16)
  • Security Hub CSPM collects security findings across services and accounts and evaluates resources against security standards.
  • A finding records a security check or security-related detection.
  • Control findings come from CSPM security checks; integrations provide other findings.
  • CSPM processes findings in AWS Security Finding Format, a common format for security finding data.
  • CSPM supports AWS Foundational Security Best Practices and standards based on CIS, PCI DSS, and NIST frameworks; a standard groups security controls.
  • Most AWS control checks use service-linked AWS Config rules that evaluate recorded resource configuration.
  • With CSPM enabled without Security Hub, manually enable AWS Config recording for the resource types required by enabled controls in every participating account and Region.
  • When both CSPM and Security Hub are enabled, CSPM automatically creates AWSConfigurationRecorderForSecurityHubCSPM for the required control resources in each applicable account and Region.
  • AWS added guidance for the CSPM service-linked configuration recorder in May 2026.
  • Daily AWS Config recording can delay change-triggered control findings until the 24-hour recording period ends.
  • EnableSecurityHub defaults EnableDefaultStandards to true; false enables CSPM without its automatically enabled standards.
  • EnableSecurityHub automatically enables AWS Foundational Security Best Practices and CIS AWS Foundations Benchmark v1.2.0 unless opted out.
  • Activate the AWS Config integration to ingest managed and custom Config rule evaluations as CSPM findings through EventBridge.
  • GuardDuty, Inspector, Macie, Firewall Manager, and IAM Access Analyzer can send findings to CSPM.
  • Systems Manager Patch Manager can send patch compliance findings to Security Hub CSPM.
  • Security Hub CSPM also receives findings from supported third-party security products and can send its findings to other AWS services and supported third-party products.

Automation rules and custom actions

Security Hub CSPM automation rules change findingsA record of a security check or a security-related detection. as they arrive. EventBridge routes finding events to external actions. A custom actionA CSPM action that sends selected findings or insight results to EventBridge. is the operator’s way to send selected findings into an EventBridge response path. Updating a finding’s status and repairing the affected resource are separate operations.

How it works

  1. In the administrator account, define an automation rule’s matching conditions and field updates. Supported actions include changing Severity, adding a Note, and updating Workflow. Workflow statusThe investigation state of a finding tracked in Workflow.Status. records investigation progress: NEW, NOTIFIED, RESOLVED, or SUPPRESSED.
  2. Rules evaluate new and updated provider findings ingested through BatchImportFindings after rule creation. A BatchUpdateFindings call does not trigger these automation rules. Rules apply in their creation Region to matching administrator and member findings.
  3. Apply rules in ascending RuleOrder. When matching rules change the same field, the later rule has the final effect. Automation updates occur before EventBridge receives the finding.
  4. For automatic response, create an EventBridge rule with source aws.securityhub and detail type Security Hub Findings - Imported. Filter finding attributes and invoke a target such as Lambda or SNS. Both import and finding update API operations can generate these events.
  5. For operator selection, create a custom action and an EventBridge rule matching its ARNAn identifier for an AWS resource such as a custom action., the Amazon Resource Name identifying the action. Select findings and choose that action. Each finding emits a separate Security Hub Findings - Custom Action event. Use the home RegionThe Region where CSPM collects linked-Region data and manages central configuration. when acting on aggregated findings.
  6. Custom action events appear in the account viewing the findings. To change a member accountAn account that grants an administrator access to view and act on its findings.’s resources, target code must assume an authorized IAM role, temporarily using that role’s permissions, in that member account.
Need Mechanism Result
Update severity or investigation status CSPM automation rule Finding fields change
Invoke an external response automatically EventBridge rule for imported findings Matching events invoke a target
Let an operator choose findings for response CSPM custom action plus EventBridge rule Selected findings emit custom action events

Exam cues

  • If the question says suppress matching findings automatically, think CSPM automation rules, because they update finding fields during ingestion.
  • If the question says start a response when a finding arrives, think an EventBridge imported-finding rule, because it invokes an external target.
  • If the question says an analyst selects findings for remediation, think custom action plus EventBridge, because the operator emits the matching action events.
  • If the question says a member resource must be changed from an administrator action, think a member account role, because the viewing account receives the event.

Remember

  • CSPM automation rules: up to 100 per administrator account; deploy in each required Region.
  • Custom actions: up to 50; select up to 20 findings at a time.
  • BatchUpdateFindings can generate EventBridge events but does not trigger CSPM automation rules.
  • SuppressionMarking a finding as requiring no action while leaving the underlying control checks enabled. does not stop controlA security requirement evaluated by one or more checks. checks. Disable an irrelevant control to stop its findings.

Trap: An automation rule that marks a finding resolved does not repair the resource. Use an external response path for remediation.

CSPM finding updates before external response
11123GuardDutyInspectorMacieSecurity Hub CSPMupdate finding fieldsEventBridgematch updated findingResponse functionexternal resource action
  1. Integrated security services send findings to CSPM.

  2. CSPM applies automation field updates before the event reaches EventBridge.

  3. An EventBridge rule matches the updated finding and invokes the response function.

Da documentação da AWS (22)
  • CSPM automation rules match findings and update supported fields such as Severity, Note, and Workflow, including suppression.
  • Only a CSPM administrator creates and manages automation rules.
  • Rules cover matching findings from the administrator and its member accounts.
  • CSPM automation rules apply only in their creation Region.
  • CSPM supports up to 100 automation rules per administrator account.
  • Rules evaluate new and updated original provider findings ingested through BatchImportFindings after rule creation.
  • BatchUpdateFindings changes do not trigger CSPM automation rules.
  • Automation rules apply in ascending RuleOrder.
  • When multiple matching rule actions change the same field, the later applied action has the final effect.
  • CSPM automation rules update findings before EventBridge rules receive and evaluate them.
  • BatchImportFindings and BatchUpdateFindings can generate Security Hub Findings - Imported events with source aws.securityhub.
  • EventBridge patterns filter finding attributes and invoke targets such as Lambda functions and SNS topics.
  • An operator selects findings and a custom action to emit separate Security Hub Findings - Custom Action events.
  • Create a custom action in CSPM and match its ARN in an EventBridge rule; ARN means Amazon Resource Name.
  • CSPM supports up to 50 custom actions.
  • An operator can select up to 20 findings for a custom action at a time.
  • Create custom actions in the home Region when managing aggregated findings there.
  • Custom action events are emitted in the account viewing the findings.
  • To change member resources, target code must assume an authorized role deployed in that member account.
  • Suppressing a finding does not stop control checks; disable an irrelevant control to stop its checks and finding generation.
  • Workflow.Status tracks investigation progress: NEW, NOTIFIED, RESOLVED, or SUPPRESSED.
  • GuardDuty, Inspector, and Macie send findings to CSPM.

Cross-account and Region aggregation

Security Hub CSPM combines two scopes: member accountAn account that grants an administrator access to view and act on its findings. relationships let an administrator manage other accounts’ findingsA record of a security check or a security-related detection., and cross-Region aggregation collects Regional data in a home RegionThe Region where CSPM collects linked-Region data and manages central configuration.. The home Region is the place to view the combined results; linked RegionsA Region connected to a home Region for aggregation and optional central configuration. supply data.

How it works

  1. In Organizations, the management account designates a delegated administratorAn account designated to manage CSPM on behalf of an organization., the member account authorized to manage CSPM for the organization. Alternatively, invite accounts manually and have them accept membership.
  2. Choose a home Region and the Regions to link. Each contributing account must have CSPM enabled where its findings originate. Linking a Region does not enable the service.
  3. CSPM replicates findings, finding updates, insightsA grouped collection of related findings used to identify an area needing attention., controlA security requirement evaluated by one or more checks. compliance statuses, and security scores to the home Region. An insight is a grouped collection of related findings.
  4. Members inherit the administrator’s aggregation settings. Sign in to the administrator account in the home Region to view the combined member findings. Members can view their own aggregated data but cannot see other members’ findings.
  5. Changes to findings replicate between home and source linked Region. If updates conflict, the most recent one wins. For manual membership, establish invitations and CSPM enablement in the home Region and every linked Region.

Exam cues

  • If the question says one findings view across accounts and Regions, think member account administration plus cross-Region aggregation, because the two mechanisms cover different scopes.
  • If the question says a linked Region has no data because CSPM is off, think enable CSPM there, because aggregation cannot produce or collect findings from a disabled service.
  • If the question says apply identical controls across Regions, think central configuration, because aggregation only collects results.

Remember

  • The home Region is also called the aggregation Region in older API terminology.
  • No linked Regions means no cross-Region replication.
  • A member sees its own data; an administrator sees associated members’ data.
  • Cross-Region finding update conflicts use the most recent update.

Trap: Linking every Region does not automatically enable CSPM in those Regions or configure their standards.

Member findings collected in the administrator home Region
findings and updates1findings and updates2Member account Alinked RegionMember account Blinked RegionAdministratorhome Region view
  1. An enabled member account generates findings in a linked Region.

  2. The administrator views associated members' replicated findings in the home Region.

Da documentação da AWS (16)
  • An administrator can view and manage associated member accounts' findings.
  • Members cannot view other members' findings.
  • The Organizations management account designates a CSPM delegated administrator, enabling trusted access and administrator management of member accounts.
  • Outside Organizations, an administrator can invite accounts; the member accepts to establish the relationship.
  • Cross-Region aggregation replicates findings, updates, insights, control compliance statuses, and security scores to a home Region.
  • Aggregation includes data only from Regions where the account has CSPM enabled.
  • Linking a Region does not enable CSPM there.
  • Finding updates replicate between the home Region and the source linked Region.
  • For conflicting updates, the most recent update wins.
  • Members inherit their administrator's aggregation settings.
  • The administrator must view the home Region to see aggregated member data.
  • For manually invited members, invitations and CSPM enablement are needed in the home Region and each linked Region.
  • A home Region can have no linked Regions; no cross-Region replication then occurs.
  • Cross-Region aggregation collects results; central configuration is the feature for configuring controls across the home and linked Regions.
  • Home Region is the current name for aggregation Region; some API operations retain the older term.
  • An insight is a grouped collection of related findings.

Central configuration policies

Security Hub CSPM central configuration applies consistent service, standard, and controlA security requirement evaluated by one or more checks. settings across an organization. A configuration policyA complete set of CSPM service, standard, and control settings associated with organization targets. is a complete set of those settings. An organizational unitA container for accounts in an organization hierarchy. (OU) groups accounts in the organization hierarchy; policy inheritanceReceiving a configuration from the closest associated parent when no direct association overrides it. lets child accounts receive their parent’s configuration.

How it works

  1. Integrate CSPM with Organizations. The management account designates a separate delegated administratorAn account designated to manage CSPM on behalf of an organization. for central configuration.
  2. Choose a home RegionThe Region where CSPM collects linked-Region data and manages central configuration. and optional linked RegionsA Region connected to a home Region for aggregation and optional central configuration.. The home Region cannot be an opt-in RegionA Region disabled for an account until explicitly enabled., a Region disabled for an account until explicitly enabled. Enable any opt-in linked Region for each account before applying its policy there.
  3. Create a policy in the home Region. Select whether CSPM is enabled, the standards to enable, the controls to enable or disable, and supported control parameters, the values that customize a check.
  4. Associate the policy with accounts, OUs, or the root. A child without direct association inherits the closest associated parent’s policy or self-managed behavior. A directly applied association overrides inheritance; settings from different policies are not merged.
  5. Apply settings across the home and all linked Regions where controls are available. Only the delegated administrator changes centrally managed settings. Self-managed accountsAn account allowed to configure its own CSPM settings separately in each Region. configure their settings separately in each Region.
  6. Apply a root policy to cover new accounts by inheritance, while allowing explicit exceptions. Dissociating a policy does not undo its changes; apply a replacement policy or switch to self-management and adjust settings.
Control selection Existing controls Newly released controls
List controls to enable Only listed controls enabled Disabled unless listed
List controls to disable All other applicable controls enabled Enabled unless excluded
Recommended policy FSBP controls with default parameters New FSBP controls enabled

Central configuration normally keeps global-resource controls, checks for resources whose scope is not limited to one Region, in the home Region. If one is unsupported there, CSPM tries a linked Region where it is supported. Configuration policies do not contain Config recorder settings: CSPM alone still needs manual recording, while CSPM with Security Hub uses the automatically created service-linked recorder.

Exam cues

  • If the question says enforce the same standards across existing and new accounts and Regions, think central configuration policies, because policies apply settings across the hierarchy and linked Regions.
  • If the question says enable future controls automatically, think a disabled-controls list, because unlisted controls remain enabled.
  • If the question says an account needs independent Regional settings, think self-managed designation, because centrally managed targets are configured only by the delegated administrator.
  • If the question says policy removed but controls stay disabled, think apply a replacement configuration, because dissociation does not restore earlier values.

Remember

  • Create and manage policies in the home Region.
  • Associate a policy before it takes effect.
  • Each account or OU uses one complete policy, with direct application overriding inheritance.
  • Policies cover home and linked Regions; they do not configure the Config recorder.

Trap: A child policy does not add selected controls to its parent’s policy. It replaces the inherited configuration with a complete policy.

Configuration policy association and inheritance
associate policy1inherit2inherit3Administratorhome RegionOrganization rootpolicy associationOUinherits policyMember accountinherits policy
  1. The delegated administrator associates a policy with the root.

  2. An OU without a direct association inherits the policy.

  3. The member inherits unless a direct policy or self-managed designation overrides inheritance.

Da documentação da AWS (21)
  • Central configuration requires Organizations integration and a delegated administrator.
  • For central configuration, the management account cannot be the delegated administrator.
  • The delegated administrator creates and manages configuration policies in the home Region.
  • The central configuration home Region cannot be an opt-in Region.
  • Linked Regions are optional for central configuration.
  • A policy applies in the home Region and all linked Regions, subject to control availability; it cannot target an arbitrary subset of those Regions.
  • Policies configure CSPM enablement, enabled standards, enabled or disabled controls, and supported custom control parameters.
  • A policy takes effect only after association with accounts, OUs, or the organization root.
  • Without direct association, an account or OU inherits the closest associated parent's policy or self-managed behavior; direct application overrides inheritance.
  • Each account or OU uses one complete configuration policy at a time.
  • Configuration settings are not merged across policies.
  • Only the delegated administrator configures centrally managed targets; self-managed accounts configure their settings separately in each Region.
  • New accounts inherit a policy associated with the root unless a different policy or self-managed designation overrides it.
  • An enabled-controls list disables unlisted controls, including newly released ones.
  • A disabled-controls list enables other applicable controls in enabled standards, including newly released ones.
  • The recommended policy enables CSPM, FSBP, and all existing and new FSBP controls with default parameters.
  • Configuration policies do not include Config recorder settings.
  • With both CSPM and Security Hub enabled, CSPM creates a service-linked recorder; CSPM alone requires manual Config recording.
  • An opt-in linked Region must be enabled for an account before its configuration policy can take effect.
  • Central configuration normally enables global-resource controls only in the home Region; if unsupported there, CSPM tries a supported linked Region.
  • Dissociating a policy does not revert its settings; apply a replacement policy or switch to self-managed and change settings.

Config recording and finding imports

Security Hub CSPM uses AWS Config for controlA security requirement evaluated by one or more checks. checks and can also import Config rule evaluations as findingsA record of a security check or a security-related detection.. These are separate paths: control checks depend on recorded resource settings, while the integration brings managed and custom rule results into CSPM.

How it works

  1. Most CSPM control checks use service-linked Config rules to evaluate recorded resource configuration. When CSPM is enabled without Security Hub, manually enable recording for the resource types required by enabled controls in every participating account and Region.
  2. If required resource types are missing from manual recording, Config.1 can report FAILED, and the affected control can produce WARNING findings.
  3. Activate the AWS Config integration to import managed and custom rule evaluations through EventBridge. The integration excludes service-linked ruleAn AWS Config rule created and managed by an AWS service for its checks. evaluations, except those from rules managed by AWS Control Tower.
  4. The integration sends evaluations performed after CSPM was enabled. CSPM does not retroactively consolidate findings generated before enablement.

Exam cues

  • If the question says Config.1 is FAILED and a control has WARNING findings under manual recording, think missing resource types in the affected account and Region, because the control needs those settings recorded.
  • If the question says import managed or custom Config rule evaluations, think activate the AWS Config integration, because CSPM control checks use a separate service-linked rule path.
  • If the question says older evaluations are missing after integration activation, think CSPM enablement time, because the integration sends evaluations performed after CSPM was enabled.

Remember

  • With CSPM alone, manually record the resource types required by enabled controls in every participating account and Region.
  • Service-linked rule evaluations are excluded from the integration, except for Control Tower-managed rules.
  • Evaluations performed before CSPM enablement are not sent by the integration.

Trap: Enabling a standard does not import managed and custom Config rule evaluations. Activate the Config integration; it does not backfill evaluations from before CSPM enablement.

Da documentação da AWS (7)
  • With CSPM enabled without Security Hub, manually enable AWS Config recording for the resource types required by enabled controls in every participating account and Region.
  • With manual recording, missing required resource recording can cause Config.1 FAILED findings and WARNING findings for the affected control.
  • Activate the AWS Config integration to ingest managed and custom Config rule evaluations as CSPM findings through EventBridge.
  • Most AWS control checks use service-linked AWS Config rules that evaluate recorded resource configuration.
  • The AWS Config integration sends evaluations performed after CSPM enablement.
  • The AWS Config integration excludes service-linked rule evaluations except those from Control Tower-managed rules.
  • CSPM does not retroactively consolidate security findings generated before it was enabled.

Flashcards

toque para virar
Resposta

·

Todos os 33 flashcards em lista

Which prerequisite supports most AWS Security Hub CSPM control checks when CSPM is enabled without Security Hub?

Enable AWS Config and record the resource types required by the controls in each participating account and Region. When both CSPM and Security Hub are enabled, CSPM creates a service-linked recorder automatically.

What does AWS Security Hub CSPM add to findings from GuardDuty, Inspector, and Macie?

A consolidated view using ASFF and security control checks grouped into standards such as FSBP, CIS, PCI DSS, and NIST.

A security team needs to review findings from multiple AWS services and accounts in one place. Which service fits?

AWS Security Hub CSPM collects security findings across services and accounts.

A team needs to evaluate AWS resources against security standards such as CIS and PCI DSS. Which service fits?

AWS Security Hub CSPM evaluates resources against standards that group security controls.

A team wants AWS Config rule evaluations included in AWS Security Hub CSPM findings. Which integration should it activate?

The AWS Config integration sends managed and custom rule evaluations as CSPM findings through EventBridge.

A team wants patch compliance alongside security control findings in AWS Security Hub CSPM. Which integration supplies it?

Systems Manager Patch Manager can send patch compliance findings to Security Hub CSPM.

For AWS Security Hub CSPM finding handling, when should a team use automation rules or EventBridge?

Use automation rules to update finding fields or suppress findings. Use EventBridge to trigger an external response such as a Lambda function or notification. A custom action lets an operator send selected findings to EventBridge.

An AWS Security Hub CSPM team wants a finding status changed automatically and a remediation function invoked. Which mechanisms fit?

Use a CSPM automation rule for the finding update and an EventBridge rule for the external response. Automation updates happen before EventBridge evaluates the finding.

An AWS Security Hub CSPM automation rule should run after a BatchUpdateFindings call. Why does it not run?

CSPM automation rules do not trigger on BatchUpdateFindings. They evaluate provider findings ingested through BatchImportFindings after rule creation.

A team needs an SNS notification for selected AWS Security Hub CSPM findings as they arrive. What should it configure?

Configure an EventBridge rule that filters finding attributes and targets an SNS topic. Match Security Hub Findings - Imported events from aws.securityhub.

A team filters Security Hub CSPM findings in EventBridge for security alerts. Do CSPM automation rule updates occur before EventBridge evaluates the findings?

Yes. CSPM automation rules update findings before EventBridge rules receive and evaluate them.

Two matching AWS Security Hub CSPM automation rules change the same finding field. Which update has the final effect?

Rules run in ascending RuleOrder, so the later matching rule has the final effect on that field.

A security team uses EventBridge to alert on AWS Security Hub CSPM findings. Can a BatchUpdateFindings call generate an imported finding event?

Yes. Both BatchUpdateFindings and BatchImportFindings can generate Security Hub Findings - Imported events.

What event source and detail type should an EventBridge rule match for automatic AWS Security Hub CSPM finding responses?

Source aws.securityhub and detail type Security Hub Findings - Imported. Add finding attribute filters to select relevant events.

How can an AWS Security Hub CSPM administrator see member findings across accounts and Regions in one place?

Associate member accounts and configure cross-Region aggregation to a home Region. View results there. Every contributing account must have CSPM enabled in the source Regions; linking alone does not enable it.

An AWS Security Hub CSPM administrator linked a Region, but an account has no findings from it because CSPM is disabled there. What is missing?

Enable CSPM in that account and Region. Aggregation does not enable the service.

An AWS Security Hub CSPM member can see its own linked-Region findings. Can it see other member accounts' findings?

No. The administrator can view member findings; members cannot view each other's findings.

An AWS Security Hub CSPM team wants the same controls enabled across linked Regions. Is findings aggregation enough?

Use central configuration. Aggregation collects results; configuration policies apply standards and control settings.

What happens when an AWS Security Hub CSPM finding has conflicting updates in the home and linked Region?

The most recent update is used. Updates replicate between the home and source linked Region.

An AWS Security Hub CSPM administrator manually invites accounts rather than using Organizations. What is required for aggregation from every linked Region?

Invite each member and enable CSPM in the home Region and every linked Region.

What data does AWS Security Hub CSPM cross-Region aggregation collect?

Findings and their updates, insights, control compliance statuses, and security scores from linked Regions into a home Region.

An AWS Security Hub CSPM team needs consistent standards and controls across OUs and Regions. How should it configure them?

Use Organizations, a delegated administrator, and central configuration. Create and associate configuration policies in the home Region; they apply in home and linked Regions.

A new account joins an OU under an AWS Security Hub CSPM root policy. Which settings apply if there is no more specific association?

It inherits the root policy. A direct policy or self-managed designation can override inherited behavior.

An AWS Security Hub CSPM team expects newly released controls to enable automatically. Which policy list should it use?

List the controls to disable. Other controls in enabled standards, including future controls, are enabled. An enabled-controls list leaves unlisted controls disabled.

An AWS Security Hub CSPM account has an explicit child policy and a parent policy. Are their settings combined?

No. Each account uses one complete configuration policy. Direct application overrides inheritance.

An AWS Security Hub CSPM policy was created but never associated with an account, OU, or root. Does it change those targets?

No. A policy takes effect only after association.

An AWS Security Hub CSPM team dissociates a policy that disabled a control. Does the control return to its previous state?

No. Dissociation does not revert settings. Apply a policy that enables the control, or use self-management to change it.

An AWS Security Hub CSPM centrally managed account wants local control settings different from its policy. Who can change its configuration?

The delegated administrator. To allow local configuration, the administrator must designate the account self-managed.

An AWS Security Hub CSPM policy links an opt-in Region, but the member account has not enabled that Region. What is required?

Enable the Region for the account before the policy can apply there. An opt-in Region cannot be the central configuration home Region.

What settings does an AWS Security Hub CSPM configuration policy specify?

CSPM enablement, enabled security standards, controls to enable or disable, and supported custom control parameters.

A team enabled AWS Security Hub CSPM without Security Hub, but a control shows WARNING and Config.1 shows FAILED. What recording issue should it check?

Check whether AWS Config records the resource type required by that control in the affected account and Region.

An AWS Security Hub CSPM team needs managed and custom AWS Config rule evaluations in the findings list. Is enabling a CSPM standard sufficient?

Activate the AWS Config integration. It imports rule evaluations through EventBridge; this is separate from the service-linked Config rules used by CSPM controls.

A team expects old AWS Config evaluations to appear after it activates the AWS Security Hub CSPM integration. What is the limitation?

The integration sends evaluations performed after CSPM was enabled. CSPM does not retroactively consolidate older findings.

Você concluiu todos os tópicos da DOP-C02!

Seu badge ficou dourado. Próximo passo: agendar a prova na AWS. Depois de passar, adicione-se ao Quem passou.

Compartilhar

Conte que você concluiu esta certificação

Concluí todos os tópicos da AWS Certified DevOps Engineer - Professional (DOP-C02) no Easy Review. Venha estudar também!