Compliance · PCI DSS
PCI DSS: find card data, and control how it moves.
PCI DSS v4.0.1 expects you to know where card data sits and to stop it moving where it should not. GuardStance supports these requirements with technical controls.
Book a demoWhich requirements does GuardStance support?
| Requirement | What it asks | How GuardStance supports it |
|---|---|---|
| Req. 3 | Protect stored account data. | Discovery finds card numbers on endpoints and file servers, with checksum checks to cut false matches. |
| 3.4.2 | When remote-access technologies are used, stop PAN being copied or relocated, except by people with documented authorization and a business need. | Clipboard, file copy, removable media and uploads are controlled on the endpoint. |
| Req. 4 | Protect cardholder data with strong cryptography during transmission. | Policy stops card data being shared without protection over email, web and cloud apps. |
| Req. 10 | Log and monitor all access to system components and cardholder data. | Events on card data are recorded with the user, the destination and what matched, and can go to your SIEM. |
| 12.10.7 | Start incident response when stored PAN is found where it is not expected. | Discovery raises the finding, and a case records what was done about it. |
GuardStance supports these requirements with technical controls. This is not legal advice; confirm legal questions with your counsel.