Class PciDssRules
java.lang.Object
com.cloudforgeci.api.core.rules.PciDssRules
- All Implemented Interfaces:
FrameworkRules<SystemContext>
@ComplianceFramework(value="PCI-DSS",
priority=20,
displayName="PCI DSS v4.0.1",
description="Validates PCI DSS v4.0.1 requirements for cardholder data protection")
public class PciDssRules
extends Object
implements FrameworkRules<SystemContext>
PCI-DSS compliance validation rules.
These rules enforce PCI-DSS requirements for environments processing cardholder data.
PCI-DSS Requirements Coverage:
- Requirement 1: Install and maintain a firewall configuration
- Requirement 2: Do not use vendor-supplied defaults
- Requirement 3: Protect stored cardholder data
- Requirement 4: Encrypt transmission of cardholder data
- Requirement 6: Develop and maintain secure systems
- Requirement 7: Restrict access to cardholder data by business need to know
- Requirement 8: Identify and authenticate access to system components
- Requirement 10: Track and monitor all access to network resources
- Requirement 11: Regularly test security systems and processes
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionControls checked across everyvalidate*method above -- seeFrameworkRules.claimedControls().Generate PCI-DSS compliance report showing which requirements are met.voidinstall(SystemContext ctx) Install PCI-DSS compliance validation rules.Methods inherited from class Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface FrameworkRules
alwaysLoad, description, displayName, frameworkId, getRequiredConfiguration, priority
-
Constructor Details
-
PciDssRules
public PciDssRules()
-
-
Method Details
-
install
Install PCI-DSS compliance validation rules. PCI-DSS applies to environments processing cardholder data. Only enforced when security profile is PRODUCTION.- Specified by:
installin interfaceFrameworkRules<SystemContext>- Parameters:
ctx- the system context containing deployment configuration and CDK stack- Since:
- 3.0.0
-
claimedControls
Controls checked across everyvalidate*method above -- seeFrameworkRules.claimedControls(). Controls the matrix marks REQUIRED for PCI-DSS but left off this list belong to always-load cross-framework classes instead (KMS_KEY_ROTATION, SECRETS_MANAGER, SECRETS_ROTATION, DATABASE_MULTI_AZ, DATABASE_PITR, DATABASE_LOGGING, CONTAINER_SECURITY, API_SECURITY, CDN_SECURITY, INSTANCE_METADATA_SECURITY, ROOT_ACCOUNT_PROTECTION, CREDENTIAL_ROTATION, SNS_KMS_ENCRYPTION, VULNERABILITY_SCANNING, BACKUP_RECOVERY, HIGH_AVAILABILITY -- see KeyManagementRules, DatabaseSecurityRules, IamSecurityRules, MessagingSecurityRules and similar), except LAMBDA_SECURITY and DATABASE_ACCESS_CONTROL, which are genuine gaps: no class anywhere checks them.- Specified by:
claimedControlsin interfaceFrameworkRules<SystemContext>- Returns:
- the control identifiers this framework's install() validates; empty if undeclared
-
generateComplianceReport
Generate PCI-DSS compliance report showing which requirements are met.
-