Mastercard SPME §10.6.1 · Jun 2022 → May 2023
Assessments for PCI Violations in Connection with ADC Events
The changes update timelines and compliance requirements for Terminal Servicers after an ADC Event. Specifically, PCI DSS revalidation is extended from 60 to 90 days post-investigation, and an additional requirement for compliance with the DESV appendix within 12 months is added, strengthening ongoing security obligations.
program: ATO Detection- authority: Mastercard SPME §6.2+ authority: Mastercard SPME §10.6.2.1risk_threshold_for_3ds_challenge: 0.5risk_score_range: [0.0, 1.0]signals:- geo_anomaly- device_fingerprint_change- velocity_breach- credential_stuffingchallenge_method: 3ds_v2persistent_risk_escalation_threshold: 3persistent_risk_lookback_days: 7agent_owner: ato_agent++ # This policy incorporates the updated Mastercard SPME §10.6.2.1 requirements,+ # including extended timelines for Terminal Servicer compliance revalidation+ # after an Account Data Compromise Event, emphasizing a 90-day PCI DSS+ # revalidation period and an added 12-month DESV appendix compliance.+ # It reinforces timely and comprehensive security procedures to mitigate+ # Account Takeover risk in line with Mastercard's updated security standards.
Account-Takeover (ATO) Detection
Account-takeover fraud occurs when a malicious actor gains unauthorized access to
a cardholder's account and initiates transactions without the cardholder's consent.
Halyard Pay implements real-time risk scoring on authentication events and enforces a
mandatory 3DS (3-D Secure) challenge for any session where the computed risk score
meets or exceeds the defined threshold.
Detection signals
The risk model incorporates multiple behavioral signals: geographic anomalies
inconsistent with a cardholder's established pattern, changes to device fingerprint,
transaction velocity breaches, and indicators of credential-stuffing activity.
Required actions
-
Evaluate each authentication event against the defined signal list in real time.
-
Compute a normalized risk score between 0.0 and 1.0.
-
If the risk score is 0.5 or greater, trigger a mandatory 3DS challenge before
authorizing the transaction.
-
Log all ATO signals and outcomes in the case management system.
-
Escalate persistent high-risk accounts to the ATO response team for manual review.
6. In the event of an Account Data Compromise (ADC), ensure that any Terminal Servicer
involved revalidates PCI DSS compliance within 90 calendar days after the forensic
investigation concludes, and demonstrate compliance with the PCI DSS Data
Encryption and Software Validation (DESV) appendix within 12 months, consistent
with Mastercard requirements (SPME §10.6.2.1).
Source authority: Mastercard SPME §6.2.§6.2, §10.6.2.1.
Account-Takeover (ATO) Detection
Account-takeover fraud occurs when a malicious actor gains unauthorized access to
a cardholder's account and initiates transactions without the cardholder's consent.
Halyard Pay implements real-time risk scoring on authentication events and enforces a
mandatory 3DS (3-D Secure) challenge for any session where the computed risk score
meets or exceeds the defined threshold.
Detection signals
The risk model incorporates multiple behavioral signals: geographic anomalies
inconsistent with a cardholder's established pattern, changes to device fingerprint,
transaction velocity breaches, and indicators of credential-stuffing activity.
Required actions
-
Evaluate each authentication event against the defined signal list in real time.
-
Compute a normalized risk score between 0.0 and 1.0.
-
If the risk score is 0.5 or greater, trigger a mandatory 3DS challenge before
authorizing the transaction.
-
Log all ATO signals and outcomes in the case management system.
-
Escalate persistent high-risk accounts to the ATO response team for manual review.
6. In the event of an Account Data Compromise (ADC), ensure that any Terminal Servicer
involved revalidates PCI DSS compliance within 90 calendar days after the forensic
investigation concludes, and demonstrate compliance with the PCI DSS Data
Encryption and Software Validation (DESV) appendix within 12 months, consistent
with Mastercard requirements (SPME §10.6.2.1).
Source authority: Mastercard SPME §6.2.§6.2, §10.6.2.1.
Source authority: Mastercard SPME §10.6.1.
--- a/policies/ato_detection/rules.yaml
+++ b/policies/ato_detection/rules.yaml
@@ -1,5 +1,5 @@
program: ATO Detection
-authority: Mastercard SPME §6.2
+authority: Mastercard SPME §10.6.2.1
risk_threshold_for_3ds_challenge: 0.5
risk_score_range: [0.0, 1.0]
signals:
@@ -11,3 +11,10 @@
persistent_risk_escalation_threshold: 3
persistent_risk_lookback_days: 7
agent_owner: ato_agent
+
+# This policy incorporates the updated Mastercard SPME §10.6.2.1 requirements,
+# including extended timelines for Terminal Servicer compliance revalidation
+# after an Account Data Compromise Event, emphasizing a 90-day PCI DSS
+# revalidation period and an added 12-month DESV appendix compliance.
+# It reinforces timely and comprehensive security procedures to mitigate
+# Account Takeover risk in line with Mastercard's updated security standards.
--- a/policies/ato_detection/policy.md
+++ b/policies/ato_detection/policy.md
@@ -20,5 +20,10 @@
authorizing the transaction.
4. Log all ATO signals and outcomes in the case management system.
5. Escalate persistent high-risk accounts to the ATO response team for manual review.
+6. In the event of an Account Data Compromise (ADC), ensure that any Terminal Servicer
+ involved revalidates PCI DSS compliance within 90 calendar days after the forensic
+ investigation concludes, and demonstrate compliance with the PCI DSS Data
+ Encryption and Software Validation (DESV) appendix within 12 months, consistent
+ with Mastercard requirements (SPME §10.6.2.1).
-Source authority: Mastercard SPME §6.2.
+Source authority: Mastercard SPME §6.2, §10.6.2.1.