cm/controlmapping
العربية
المصادر
الإطار

PCI DSS v4.0.1

ما هو

معيار أمان بيانات صناعة بطاقات الدفع، الذي تصونه PCI SSC: 12 متطلبًا رئيسيًا لحماية بيانات الحسابات المالية للدفع. الإصدار 4.0.1 (يونيو 2024) هو الإصدار الحالي، وقد أصبحت المتطلبات الواردة في الإصدار v4.0 التي كان تاريخ سريانها مستقبليًا إلزامية اعتبارًا من 31 مارس 2025.

من يحتاجه

أي تاجر أو مزود خدمة يخزن بيانات حاملي البطاقات أو يعالجها أو ينقلها، أو يمكنه التأثير في أمانها. تفرض ذلك العلامات التجارية للبطاقات من خلال عقود الجهات المستحوذة، وهو ليس قانونًا.

كيف يُقيَّم

بحسب حجم المعاملات وقواعد العلامات التجارية للبطاقات، إما تقرير الامتثال الذي يعده مقيّم أمن معتمد (QSA)، أو استبيان التقييم الذاتي، ويُرفق بكل منهما شهادة الامتثال (AoC)، إضافةً إلى فحوصات ربعية للثغرات الخارجية يجريها مورّد فحص معتمد (ASV). يُجرى التقييم سنويًا.

260
المتطلبات
77
مُطابَق مع إطار آخر
92%
الموضوعات المغطاة (46/50)

المقارنات

المتطلبات

تُعرض معرّفات المتطلبات وعناوينها كما تنشرها كل جهة معيارية، باللغة الإنجليزية.

متطلبات PCI DSS v4.0.1
IDالمتطلبالموضوعاتمُطابَق في
Requirement 1: Install and maintain network security controls · 19
1.1.1Network security policies documented and kept current—0
1.1.2Roles for network security controls assigned—0
1.2.1Configuration standards for network security controlsجدار الحماية / تجزئة الشبكة9 من 13
1.2.2Network connection changes go through change control—لا شيء
1.2.3Accurate network diagram maintainedجدار الحماية / تجزئة الشبكة9 من 13
1.2.4Accurate account-data flow diagram maintained—0
1.2.5Allowed services, protocols and ports approved—لا شيء
1.2.6Security features defined for insecure services—لا شيء
1.2.7Network security control rules reviewed every six months—لا شيء
1.2.8Network security control configuration files secured—لا شيء
1.3.1Inbound traffic to the CDE restrictedجدار الحماية / تجزئة الشبكة9 من 13
1.3.2Outbound traffic from the CDE restricted—لا شيء
1.3.3Network controls between wireless networks and the CDE—لا شيء
1.4.1Network controls between trusted and untrusted networksجدار الحماية / تجزئة الشبكة9 من 13
1.4.2Inbound traffic from untrusted networks restricted—لا شيء
1.4.3Anti-spoofing measures in place—لا شيء
1.4.4Stored cardholder data not reachable from untrusted networks—لا شيء
1.4.5Internal IP addresses and routing not disclosed—لا شيء
1.5.1Controls on devices connecting to untrusted networks and the CDE—لا شيء
Requirement 2: Apply secure configurations to all system components · 11
2.1.1Secure configuration policies documented and kept current—0
2.1.2Roles for secure configuration assigned—0
2.2.1System configuration standards developed and maintainedالإعدادات الآمنة9 من 13
2.2.2Vendor default accounts managed or removedالإعدادات الآمنة9 من 13
2.2.3Functions with different security levels kept apart—لا شيء
2.2.4Only necessary services and functions enabled—لا شيء
2.2.5Insecure services justified and secured—لا شيء
2.2.6System security parameters set to prevent misuse—لا شيء
2.2.7Non-console administrative access encrypted—لا شيء
2.3.1Wireless vendor defaults changed—0
2.3.2Wireless keys changed when key holders leave—لا شيء
Requirement 3: Protect stored account data · 29
3.1.1Stored account data policies documented and kept current—0
3.1.2Roles for protecting stored account data assigned—0
3.2.1Account data storage minimised, with retention and disposalحماية البيانات11 من 13
3.3.1Sensitive authentication data not kept after authorisationحماية البيانات11 من 13
3.3.1.1Full track data not kept after authorisation—لا شيء
3.3.1.2Card verification code not kept after authorisation—لا شيء
3.3.1.3PIN and PIN block not kept after authorisation—لا شيء
3.3.2Sensitive authentication data encrypted before authorisation—لا شيء
3.3.3Issuer storage of sensitive authentication data limited and protected—لا شيء
3.4.1PAN masked when displayedحماية البيانات11 من 13
3.4.2PAN copying prevented over remote-access technologiesDLP7 من 13
3.5.1PAN rendered unreadable wherever storedالتشفير10 من 13
3.5.1.1Hashes of PAN are keyed cryptographic hashes—لا شيء
3.5.1.2Disk-level encryption used only where it suffices—لا شيء
3.5.1.3Disk encryption access managed separately from OS access—0
3.6.1Procedures protect keys that secure stored account dataالتشفير10 من 13
3.6.1.1Service providers document their cryptographic architecture—0
3.6.1.2Secret and private keys stored in approved forms—0
3.6.1.3Cleartext key components accessible to fewest custodians—0
3.6.1.4Keys stored in the fewest possible locations—0
3.7.1Key management: strong key generationالتشفير10 من 13
3.7.2Key management: secure key distribution—لا شيء
3.7.3Key management: secure key storage—لا شيء
3.7.4Key management: key changes at end of cryptoperiodالتشفير10 من 13
3.7.5Key management: retiring weakened or compromised keys—لا شيء
3.7.6Key management: split knowledge and dual control—لا شيء
3.7.7Key management: preventing unauthorised key substitution—لا شيء
3.7.8Key custodians formally acknowledge their responsibilities—لا شيء
3.7.9Service providers give customers key-handling guidance—لا شيء
Requirement 4: Protect cardholder data with strong cryptography during transmission · 6
4.1.1Data-in-transit policies documented and kept current—0
4.1.2Roles for protecting data in transit assigned—0
4.2.1Strong cryptography for PAN over open, public networksالتشفير10 من 13
4.2.1.1Inventory of trusted keys and certificates keptالتشفير10 من 13
4.2.1.2Strong cryptography on wireless networks carrying PAN—لا شيء
4.2.2PAN secured when sent by end-user messaging—لا شيء
Requirement 5: Protect all systems and networks from malicious software · 13
5.1.1Anti-malware policies documented and kept current—0
5.1.2Roles for malware protection assigned—0
5.2.1Anti-malware deployed on system componentsحماية نقاط النهاية10 من 13
5.2.2Anti-malware detects, removes or contains known malwareحماية نقاط النهاية10 من 13
5.2.3Systems without anti-malware periodically re-evaluated—0
5.2.3.1Re-evaluation frequency set by targeted risk analysis—0
5.3.1Anti-malware kept up to date—لا شيء
5.3.2Periodic scans or continuous behavioural analysisحماية نقاط النهاية10 من 13
5.3.2.1Scan frequency set by targeted risk analysis—0
5.3.3Removable media scanned or analysed—لا شيء
5.3.4Anti-malware audit logs enabled and retained—لا شيء
5.3.5Users cannot disable or alter anti-malware—لا شيء
5.4.1Mechanisms to detect and protect against phishingأمن البريد الإلكتروني8 من 13
Requirement 6: Develop and maintain secure systems and software · 19
6.1.1Secure systems and software policies documented—0
6.1.2Roles for secure systems and software assigned—0
6.2.1Bespoke and custom software developed securelyالتطوير الآمن8 من 13
6.2.2Developers trained in secure software developmentالتطوير الآمن8 من 13
6.2.3Custom code reviewed before releaseالتطوير الآمن, أمن واجهات برمجة التطبيقات8 من 13
6.2.3.1Manual code reviews approved by someone else—0
6.2.4Coding techniques prevent common software attacksأمن واجهات برمجة التطبيقات4 من 13
6.3.1Vulnerabilities identified and risk-rankedإدارة الثغرات, استخبارات التهديدات, إدارة الرقع13 من 13
6.3.2Inventory of custom software and its componentsمخاطر سلسلة التوريد, إدارة الأصول13 من 13
6.3.3Security patches installed promptlyإدارة الرقع10 من 13
6.4.1Public web applications protected against attacksأمن تطبيقات الويب6 من 13
6.4.2Automated solution blocks attacks on public web appsWAF5 من 13
6.4.3Payment page scripts authorised and integrity-checkedأمن تطبيقات الويب6 من 13
6.5.1Production changes follow change control procedures—لا شيء
6.5.2PCI DSS requirements re-confirmed after significant changes—لا شيء
6.5.3Pre-production environments separated from production—لا شيء
6.5.4Duties separated between production and pre-production—لا شيء
6.5.5Live PANs not used in pre-production—لا شيء
6.5.6Test data and accounts removed before go-live—لا شيء
Requirement 7: Restrict access to system components and cardholder data by business need to know · 12
7.1.1Access restriction policies documented and kept current—0
7.1.2Roles for access restriction assigned—0
7.2.1Access control model definedالتحكم في الوصول, الثقة المعدومة11 من 13
7.2.2Access assigned by job function and least privilegeالتحكم في الوصول, الوصول المميز12 من 13
7.2.3Privileges approved by authorised personnel—لا شيء
7.2.4User accounts and privileges reviewed every six monthsالتحكم في الوصول11 من 13
7.2.5System and application accounts least privilege—لا شيء
7.2.5.1System and application account access periodically reviewed—0
7.2.6Access to cardholder data repositories restricted—لا شيء
7.3.1Access control system restricts access by need—لا شيء
7.3.2Access control system enforces assigned permissions—لا شيء
7.3.3Access control system set to deny by default—لا شيء
Requirement 8: Identify users and authenticate access to system components · 29
8.1.1Identification and authentication policies documented—0
8.1.2Roles for identification and authentication assigned—0
8.2.1Every user has a unique IDالتحكم في الوصول11 من 13
8.2.2Shared or generic accounts only by documented exception—0
8.2.3Service providers use unique credentials per customer—لا شيء
8.2.4User ID changes authorised and controlled—لا شيء
8.2.5Access revoked immediately on termination—0
8.2.6Inactive user accounts disabled within 90 days—0
8.2.7Third-party remote access accounts enabled only when needed—لا شيء
8.2.8Re-authentication after 15 minutes idle—0
8.3.1User and admin access requires an authentication factorالثقة المعدومة7 من 13
8.3.2Authentication factors unreadable in transit and storage—لا شيء
8.3.3Identity verified before changing authentication factors—لا شيء
8.3.4Account lockout after repeated failed attempts—لا شيء
8.3.5First-use and reset passwords unique and changed—0
8.3.6Minimum password length and complexity—0
8.3.7Recent passwords cannot be reused—0
8.3.8Authentication guidance communicated to users—0
8.3.9Password-only access: change every 90 days or analyse risk—0
8.3.10Service providers give customers password guidance—0
8.3.10.1Service provider customer passwords: rotation or analysis—0
8.3.11Tokens, smart cards and certificates assigned to individuals—لا شيء
8.4.1MFA for non-console administrative access to the CDEالمصادقة متعددة العناصر10 من 13
8.4.2MFA for all access into the CDEالمصادقة متعددة العناصر10 من 13
8.4.3MFA for remote network accessالمصادقة متعددة العناصر10 من 13
8.5.1MFA systems configured to resist misuseالمصادقة متعددة العناصر10 من 13
8.6.1Interactive use of system accounts managed—لا شيء
8.6.2No hard-coded passwords for system accounts—0
8.6.3System account passwords protected and changed—0
Requirement 9: Restrict physical access to cardholder data · 27
9.1.1Physical security policies documented and kept current—0
9.1.2Roles for physical security assigned—0
9.2.1Facility entry controls restrict CDE accessالأمن المادي8 من 13
9.2.1.1Access to sensitive areas monitored by camera or access controlالأمن المادي8 من 13
9.2.2Publicly accessible network jacks restricted—لا شيء
9.2.3Physical access to network hardware restrictedالأمن المادي8 من 13
9.2.4Consoles in sensitive areas locked when unattended—0
9.3.1Personnel physical access authorised and managedالأمن المادي8 من 13
9.3.1.1Sensitive-area access authorised and revoked promptlyالأمن المادي8 من 13
9.3.2Visitor access authorised, escorted and identifiableالأمن المادي8 من 13
9.3.3Visitor badges returned or deactivated—لا شيء
9.3.4Visitor log maintained and retained—لا شيء
9.4.1Media with cardholder data physically secured—لا شيء
9.4.1.1Offline backup media stored securelyالنسخ الاحتياطي والاستعادة11 من 13
9.4.1.2Security of offline backup location reviewed annually—0
9.4.2Media classified by data sensitivityتصنيف البيانات9 من 13
9.4.3Media sent off site tracked and secured—لا شيء
9.4.4Management approves media moved off site—لا شيء
9.4.5Inventory logs of electronic media kept—لا شيء
9.4.5.1Electronic media inventories at least annually—لا شيء
9.4.6Hard-copy media destroyed when no longer needed—0
9.4.7Electronic media destroyed or made unrecoverable—0
9.5.1Card-reading (POI) devices protected from tampering—لا شيء
9.5.1.1Inventory of POI devices kept—0
9.5.1.2POI devices inspected for tampering—0
9.5.1.2.1Inspection frequency set by targeted risk analysis—0
9.5.1.3Staff trained to spot POI tampering—لا شيء
Requirement 10: Log and monitor all access to system components and cardholder data · 27
10.1.1Logging and monitoring policies documented—0
10.1.2Roles for logging and monitoring assigned—0
10.2.1Audit logs enabled and activeالتسجيل والتدقيق, التهديدات الداخلية11 من 13
10.2.1.1Logs capture user access to cardholder data—لا شيء
10.2.1.2Logs capture administrative actions—لا شيء
10.2.1.3Logs capture access to audit logs—لا شيء
10.2.1.4Logs capture invalid access attempts—لا شيء
10.2.1.5Logs capture credential and privilege changes—لا شيء
10.2.1.6Logs capture starting, stopping or pausing logging—لا شيء
10.2.1.7Logs capture system-level object changes—لا شيء
10.2.2Log entries record who, what, when, where and outcome—0
10.3.1Read access to logs limited to need—0
10.3.2Logs protected from modificationالتسجيل والتدقيق, الطب الشرعي الرقمي10 من 13
10.3.3Logs promptly backed up to a central server—0
10.3.4File-integrity monitoring on logs—0
10.4.1Security event and critical logs reviewed dailyالمراقبة المستمرة, SIEM / SOC10 من 13
10.4.1.1Automated mechanisms for log reviewاكتشاف الشذوذ9 من 13
10.4.2Other logs reviewed periodically—لا شيء
10.4.2.1Review frequency set by targeted risk analysis—0
10.4.3Exceptions and anomalies addressed—لا شيء
10.5.1Audit logs retained 12 months, three immediately availableالتسجيل والتدقيق10 من 13
10.6.1System clocks synchronisedالتسجيل والتدقيق10 من 13
10.6.2Time configuration correct and consistent—لا شيء
10.6.3Time settings protected from change—0
10.7.1Service providers detect security control failures—0
10.7.2Critical security control failures detected and reported—0
10.7.3Security control failures responded to promptly—لا شيء
Requirement 11: Test security of systems and networks regularly · 21
11.1.1Security testing policies documented and kept current—0
11.1.2Roles for security testing assigned—0
11.2.1Wireless access points detected and unauthorised ones handled—0
11.2.2Inventory of authorised wireless access points—لا شيء
11.3.1Internal vulnerability scans every three monthsإدارة الثغرات13 من 13
11.3.1.1Lower-ranked vulnerabilities handled by risk analysis—0
11.3.1.2Internal scans use authenticated scanning—لا شيء
11.3.1.3Internal scans after significant changes—لا شيء
11.3.2External ASV scans every three monthsإدارة الثغرات13 من 13
11.3.2.1External scans after significant changes—لا شيء
11.4.1Penetration testing methodology defined—لا شيء
11.4.2Internal penetration test at least annually—لا شيء
11.4.3External penetration test at least annually—لا شيء
11.4.4Penetration test findings corrected and retested—0
11.4.5Segmentation controls tested at least annually—لا شيء
11.4.6Service providers test segmentation every six months—لا شيء
11.4.7Multi-tenant providers support customer penetration tests—لا شيء
11.5.1Intrusion detection or prevention on network trafficكشف التسلل9 من 13
11.5.1.1Service providers detect covert malware communication—لا شيء
11.5.2Change-detection on critical files—لا شيء
11.6.1Payment page changes and tampering detected—0
Requirement 12: Support information security with organizational policies and programs · 37
12.1.1Information security policy established and publishedسياسة الحوكمة9 من 13
12.1.2Security policy reviewed at least annuallyسياسة الحوكمة9 من 13
12.1.3Security roles and responsibilities definedالأدوار والمسؤوليات9 من 13
12.1.4Executive responsibility for information security assignedالأدوار والمسؤوليات9 من 13
12.2.1Acceptable use policies for end-user technologies—لا شيء
12.3.1Targeted risk analysis for flexible-frequency requirementsإدارة المخاطر, تقييم المخاطر10 من 13
12.3.2Targeted risk analysis for customised approach—0
12.3.3Cipher suites and protocols reviewed annually—0
12.3.4Hardware and software technologies reviewed annually—0
12.4.1Service providers: executive responsibility for PCI DSS compliance—لا شيء
12.4.2Service providers: quarterly reviews of operational tasksالامتثال10 من 13
12.4.2.1Service providers: quarterly review results documented—0
12.5.1Inventory of in-scope system componentsإدارة الأصول13 من 13
12.5.2PCI DSS scope confirmed annually and on changeبيئة الأعمال5 من 13
12.5.2.1Service providers confirm scope every six months—لا شيء
12.5.3Service providers review scope after organisational change—0
12.6.1Formal security awareness programmeالتوعية والتدريب10 من 13
12.6.2Awareness programme reviewed annually—لا شيء
12.6.3Awareness training on hire and at least annuallyالتوعية والتدريب10 من 13
12.6.3.1Training covers phishing and social engineering—لا شيء
12.6.3.2Training covers acceptable use of technology—لا شيء
12.7.1Personnel screened before hireالتهديدات الداخلية8 من 13
12.8.1List of third-party service providers keptمخاطر سلسلة التوريد, أمن السحابة, إدارة مخاطر الموردين12 من 13
12.8.2Written agreements with service providersإدارة مخاطر الموردين10 من 13
12.8.3Due diligence before engaging service providersإدارة مخاطر الموردين10 من 13
12.8.4Service provider compliance monitored annuallyإدارة مخاطر الموردين10 من 13
12.8.5Responsibilities split with each provider documentedأمن السحابة, إدارة مخاطر الموردين12 من 13
12.9.1Service providers acknowledge responsibilities to customers—0
12.9.2Service providers support customer compliance requests—0
12.10.1Incident response plan ready to activateالاستجابة للحوادث, التخفيف, الإبلاغ, تخطيط الاستعادة, استمرارية الأعمال, التعافي من الكوارث12 من 13
12.10.2Incident response plan reviewed and tested annuallyالاستجابة للحوادث12 من 13
12.10.3Incident response staff available around the clockالاستجابة للحوادث12 من 13
12.10.4Incident response staff trainedالاستجابة للحوادث12 من 13
12.10.4.1Training frequency set by targeted risk analysis—0
12.10.5Plan covers alerts from security monitoring—0
12.10.6Plan updated from lessons learned and industry changesالدروس المستفادة9 من 13
12.10.7Procedures for PAN found where it shouldn't be—0
Appendix A: additional requirements · 10
A1.1.1Multi-tenant providers: separate provider and customer environments—لا شيء
A1.1.2Multi-tenant providers: customers confined to their own environment—لا شيء
A1.1.3Multi-tenant providers: customers reach only their own data—لا شيء
A1.1.4Multi-tenant providers: separation tested every six months—لا شيء
A1.2.1Multi-tenant providers: audit logging for each customer—لا شيء
A1.2.2Multi-tenant providers: support customer forensic investigations—لا شيء
A1.2.3Multi-tenant providers: report suspected incidents to customers—لا شيء
A2.1.1POI terminals using SSL or early TLS not exploitable—لا شيء
A2.1.2Service providers: migration plan off SSL and early TLS—لا شيء
A2.1.3Service providers offer a secure connection option—لا شيء

تغطية الموضوع

الموضوعات ذات متطلبات PCI DSS المربوطة (46):

لا يوجد ربط في بياناتنا لا يوجد متطلب PCI DSS (4):