Sign In
Explore
AWS
Azure
GCP
Information Security Policy
PCI Assessment
Risk Assessment
SOC 2 Audit
Audit
Start A Scan
Information Security Policy Review
PCI Report Analysis
Risk Assessment Review
SOC 2 Report Analysis
Learn
Contact
Pricing
Sign In
PCI Requirement 7.2.2 – Assignment of Privileges Based on Job Function
Copy Link
Related Videos
10.6.1 – Review Daily All Security Events and Logs of All System Components.mp4
Copy Link
10.6.2 – Review Logs of All Other System Components Based Policies and Risk Management Strategy
Copy Link
10.6.3 –Follow Up Exceptions and Anomalies Identified During the Review Process
Copy Link
5 Benchmarks of Role-Based Access Control Service Accounts
Copy Link
5 Focus Areas for AWS Compliance
Copy Link
AWS Functions to Restrict Database Access
Copy Link
AWS Password Best Practices
Copy Link
AWS Password Expiration Policies
Copy Link
AWS Password Reuse Policy
Copy Link
Access Control Using IAM Instance Roles
Copy Link
Allow Azure Services Access to Storage Accounts
Copy Link
Assign Access Based on Business Need to Know
Copy Link
Assign Appropriate Contacts to Essential Roles
Copy Link
Assigning Information Security Management Responsibility
Copy Link
Attaching IAM Policies to Groups or Roles
Copy Link
Avoid Use of the Root Account
Copy Link
Basics of Role Assumption
Copy Link
Best Practices for Change Management in AWS
Copy Link
Best Practices for Password Parameters
Copy Link
Create a Review Process of Guest Users
Copy Link
Define Acceptable Use of Technology Part 1
Copy Link
Defining Resources in IAM Policies
Copy Link
Defining Resources in S3 Bucket Policies
Copy Link
Defining Roles and Responsibilities in AWS
Copy Link
Developing a Process for User Authentication
Copy Link
Disable Caching of Second Factor of Authentication Beyond One Day
Copy Link
Disable Public Access Level for Storage Accounts with Blob Containers
Copy Link
Disabling Unused Credentials
Copy Link
Do Not Allow Users to Remember MFA on Devices They Trust
Copy Link
Do Not Enable Serial Ports for VM Instance
Copy Link
Do Not Use Project-Wide SSH Keys When Authenticating Instances
Copy Link
Documenting a Systems Inventory in AWS
Copy Link
Enable Multi-Factor Authentication for Non-Service Accounts
Copy Link
Enable Multifactor Authentication for Administrators
Copy Link
Enabling MFA for All IAM Users
Copy Link
Encrypt Dataproc Cluster Using Customer Managed Encryption Key
Copy Link
Enforce Multifactor Authentication for All Users
Copy Link
Enforce Separation of Duties When Assigning Service Account Roles
Copy Link
Enforce Separation with Access Controls
Copy Link
Enforcing Strong Encryption in AWS
Copy Link
Ensure Corporate Login Credentials are Used
Copy Link
Ensure Notifications are Enabled for Password Resets
Copy Link
Ensure Service Accounts Can't Access Admin Privileges
Copy Link
Establish Policy to Disconnect Remote Sessions
Copy Link
Establish Policy to Disconnect Vendor Sessions When Not in Use
Copy Link
Establishing the Scope of your Cardholder Data Environment
Copy Link
Evaluate and Restrict UDP Access from the Internet
Copy Link
Exclusively Use GCP-Managed Service Account Keys
Copy Link
GKE Authentication and Authorization Best Practices
Copy Link
How to Attach IAM Policies to Groups or Roles
Copy Link
How to Check MFA in a Credential Report
Copy Link
How to Check Use of the Root Account
Copy Link
How to Find Administrative Privileges in IAM Policies
Copy Link
How to House Multiple Accounts Within an AWS Organization
Copy Link
How to Modify Password Complexity in a Password Policy
Copy Link
How to Modify Permissions to EBS Snapshots
Copy Link
How to Prevent Password Reuse in a Password Policy
Copy Link
How to Use S3 Bucket Policies
Copy Link
IAM Policies for Account Authentication
Copy Link
IAM Policies that Address Administrative Privileges
Copy Link
Identifying Unused Credentials in a Credential Report
Copy Link
Identity and Access Management Benchmarks in GKE
Copy Link
Introduction to Amazon S3 Access Points
Copy Link
Introduction to IAM Access Analyzer
Copy Link
Introduction to PCI DSS Requirement 1
Copy Link
Introduction to PCI DSS: What is the Payment Card Industry Data Security Standard
Copy Link
Introduction to PCI Requirement 2.mp4
Copy Link
MFA for API Calls
Copy Link
Notify Admins of Other Admin Password Resets
Copy Link
Only Allow Administrators to Delete Locked Resources
Copy Link
Only Allow Approved Employees to Invite Guests
Copy Link
PCI DSS Requirement 1.1.1 - Implementing a Change Control Program
Copy Link
PCI DSS Requirement 1.1.2 and 1.1.3 - Network Documentation Best Practices
Copy Link
PCI DSS Requirement 1.1.4 - Establishing a Firewall and DMZ
Copy Link
PCI DSS Requirement 1.1.5 Defining Roles and Responsibilities for Managing Network Components
Copy Link
PCI DSS Requirement 1.1.6 Documentation of Business Justification & Approval for use of all Services, Ports and Protocols
Copy Link
PCI DSS Requirement 1.1.7 - Review Firewall and Router Rule Sets
Copy Link
PCI DSS Requirement 1.2 Restrict Connections to Untrusted Networks
Copy Link
PCI DSS Requirement 1.2.1 Restrict Traffic to that which is Necessary
Copy Link
PCI DSS Requirement 1.2.2 Secure and Synchronize Router Configuration Files
Copy Link
PCI DSS Requirement 1.2.3 Install Firewalls Between all Wireless Networks and the CDE
Copy Link
PCI DSS Requirement 1.3 Examine Firewall and Router Configurations
Copy Link
PCI DSS Requirement 1.3.1 - Establishing a DMZ
Copy Link
PCI DSS Requirement 1.3.2 Limit Inbound Internet Traffic
Copy Link
PCI DSS Requirement 1.3.3 - Implement Anti Spoofing Measures
Copy Link
PCI DSS Requirement 1.3.4 - Deny Unauthorized Outbound Traffic
Copy Link
PCI DSS Requirement 1.3.5 - Permit Only Established Connections into the Network
Copy Link
PCI DSS Requirement 1.3.6 Segregate the CDE from the DMZ
Copy Link
PCI DSS Requirement 1.3.7 Do Not Disclose Private IP Addresses
Copy Link
PCI DSS Requirement 1.4 Install Personal Firewall Software
Copy Link
PCI DSS Requirement 1.5 Ensure Security Policies are Known to all Affected Parties
Copy Link
PCI Requirement 10 – Track and Monitor all Access to Network Resources and Cardholder Data
Copy Link
PCI Requirement 10.1 – Implement Audit Trails to Link all Access to System Components
Copy Link
PCI Requirement 10.2 – Implement Automated Audit Trails for all System Components
Copy Link
PCI Requirement 10.2.1 – All Individual User Accesses to Cardholder Data
Copy Link
PCI Requirement 10.2.2 – All Actions Taken by Any Individual with Root or Administrative Privileges
Copy Link
PCI Requirement 10.2.3 – Access to All Audit Trails
Copy Link
PCI Requirement 10.2.4 – Invalid Logical Access Attempts.mp4
Copy Link
PCI Requirement 10.2.5 – Use of and Changes to Identification Accounts with Root Privileges
Copy Link
PCI Requirement 10.2.6 – Initialization, Stopping, or Pausing of the Audit Logs
Copy Link
PCI Requirement 10.2.7 – Creation and Deletion of System-Level Objects
Copy Link
PCI Requirement 10.3 – Record at Least the Following Audit Trail Entries for All System Components
Copy Link
PCI Requirement 10.3.1 – User Identification
Copy Link
PCI Requirement 10.3.2 – Type of Event
Copy Link
PCI Requirement 10.3.3 – Date and Time
Copy Link
PCI Requirement 10.3.4 – Success or Failure Indication
Copy Link
PCI Requirement 10.3.5 – Origination of Event
Copy Link
PCI Requirement 10.3.6 – Identity or Name of Affected Data, System Component, or Resource
Copy Link
PCI Requirement 10.4 – Using Time-Synchronization Technology, Synchronize All Critical Systems
Copy Link
PCI Requirement 10.4.1 – Critical Systems Have the Correct and Consistent Time
Copy Link
PCI Requirement 10.4.2 – Time Data is Protected
Copy Link
PCI Requirement 10.4.3 – Time Settings Are Received from Industry-Accepted Time Sources
Copy Link
PCI Requirement 10.5 – Secure Audit Trails so They Cannot Be Altered
Copy Link
PCI Requirement 10.5.1 – Limit Viewing of Audit Trails to Those with a Job-Related Need
Copy Link
PCI Requirement 10.5.2 – Protect Audit Trail Files from Unauthorized Modifications
Copy Link
PCI Requirement 10.5.3 – Promptly Back Up Audit Trail Files to a Centralized Log Server
Copy Link
PCI Requirement 10.5.4 – Write Logs for External-Facing Technologies onto a Secure Device
Copy Link
PCI Requirement 10.5.5 – Use File-Integrity Monitoring or Change-Detection Software on Logs
Copy Link
PCI Requirement 10.6 – Review Logs and Security Events for All System Components
Copy Link
PCI Requirement 10.7 – Retain Audit Trail History for at Least One Year, with Three Months Available
Copy Link
PCI Requirement 10.8 –Implement a Process for the Detection of Failures of Critical Control Systems
Copy Link
PCI Requirement 10.8.1 –Respond to Failures of Any Critical Security Controls in a Timely Manner
Copy Link
PCI Requirement 10.9 – Document Policies & Procedures for Monitoring Access to Network Resources
Copy Link
PCI Requirement 11 - Regularly Test Security Systems & Processes
Copy Link
PCI Requirement 11.1 – Implement Processes to Test for the Presence of Wireless Access Points
Copy Link
PCI Requirement 11.1.2 – Unauthorized Wireless Access Points Detection
Copy Link
PCI Requirement 11.2 – Quarterly Internal & External Vulnerability Scans
Copy Link
PCI Requirement 11.2.1 – Perform Quarterly Internal Vulnerability Scans
Copy Link
PCI Requirement 11.2.2 – Perform Quarterly External Vulnerability Scans
Copy Link
PCI Requirement 11.2.3 – Perform Internal and External Scans and Rescans as Needed
Copy Link
PCI Requirement 11.3 – Implement a Methodology for Penetration Testing
Copy Link
PCI Requirement 11.3.1 – Perform External Penetration Testing at Least Annually
Copy Link
PCI Requirement 11.3.2 – Perform Internal Penetration Testing at Least Annually
Copy Link
PCI Requirement 11.3.3 – Exploitable Vulnerabilities Found During Penetration Testing are Corrected
Copy Link
PCI Requirement 11.3.4 – Perform Penetration Tests if Segmentation is Used
Copy Link
PCI Requirement 11.3.4.1 – Confirm PCI DSS Scope by Performing Penetration Testing on Segmentation
Copy Link
PCI Requirement 11.4 – Use Intrusion-Detection and/or Intrusion-Prevention Techniques
Copy Link
PCI Requirement 11.5 – Deploy a Change-Detection Mechanisms to Alert Personnel
Copy Link
PCI Requirement 11.5.1 – Implement a Process to Respond to Change-Detection Solution Alerts
Copy Link
PCI Requirement 11.6 – Ensure Security Policies for Security Monitoring are Documented
Copy Link
PCI Requirement 12- Maintain a Policy that Addresses Information Security for All Personnel
Copy Link
PCI Requirement 12.1 & 12.1.1 – Establish, Publish, Maintain, and Disseminate a Security Policy
Copy Link
PCI Requirement 12.10 – Implement an Incident Response Plan
Copy Link
PCI Requirement 12.10.1 – Create the Incident Response Plan to Be Implemented
Copy Link
PCI Requirement 12.10.2 – Review and Test the Plan at Least Annually
Copy Link
PCI Requirement 12.10.3 – Designate Specific Personnel to Be Available on a 24/7 Basis
Copy Link
PCI Requirement 12.10.4 – Provide Training to Staff with Security Breach Responsibilities
Copy Link
PCI Requirement 12.10.5 – Include Alerts from Security Monitoring Systems
Copy Link
PCI Requirement 12.10.6 – Develop a Process to Modify and Evolve the Incident Response Plan
Copy Link
PCI Requirement 12.11 – Perform Reviews to Confirm Personnel Are Following Security Policies
Copy Link
PCI Requirement 12.11.1 – Maintain Documentation of Quarterly Review Process
Copy Link
PCI Requirement 12.2 – Implement a Risk Assessment Process
Copy Link
PCI Requirement 12.3 – Develop Usage Policies for Critical Technologies
Copy Link
PCI Requirement 12.3.1 – Explicit Approval by Authorized Parties
Copy Link
PCI Requirement 12.3.10 – Prohibit the Moving of Cardholder Data onto Local Hard Drives
Copy Link
PCI Requirement 12.3.2 – Authentication for Use of the Technology
Copy Link
PCI Requirement 12.3.3 – A List of All Such Devices and Personnel with Access
Copy Link
PCI Requirement 12.3.4 – A Method to Accurately Determine Owner, Contact Information, and Purpose
Copy Link
PCI Requirement 12.3.5 – Acceptable Uses of the Technology
Copy Link
PCI Requirement 12.3.6 – Acceptable Network Locations for the Technologies
Copy Link
PCI Requirement 12.3.7 – List of Company-Approved Products
Copy Link
PCI Requirement 12.3.8 – Automatic Disconnect of Sessions for Remote-Access Technologies
Copy Link
PCI Requirement 12.3.9 – Activation of Remote-Access Technologies for Vendors and Business Partners
Copy Link
PCI Requirement 12.4 – Ensure Security Policies & Procedures Define Responsibilities for All
Copy Link
PCI Requirement 12.4.1 – Executive Management Shall Establish Responsibility
Copy Link
PCI Requirement 12.5 – Assign Information Security Management Responsibilities to a Team
Copy Link
PCI Requirement 12.5.1 – Establish, Document, and Distribute Security Policies and Procedures
Copy Link
PCI Requirement 12.5.2 – Monitor and Analyze Security Alerts and Distribute to Appropriate Personnel
Copy Link
PCI Requirement 12.5.3 – Establish Security Incident Response and Escalation Procedures
Copy Link
PCI Requirement 12.5.4 – Administer User Accounts, Including Additions, Deletions, and Modifications
Copy Link
PCI Requirement 12.5.5 – Monitor and Control All Access to Data
Copy Link
PCI Requirement 12.6 – Implement a Formal Security Awareness Program
Copy Link
PCI Requirement 12.6.1 – Educate Personnel Upon Hire and at Least Annually
Copy Link
PCI Requirement 12.6.2 – Require Personnel to Read and Understand Security Policies and Procedures
Copy Link
PCI Requirement 12.7 – Screen Personnel Prior to Hire to Minimize the Risk of Attacks
Copy Link
PCI Requirement 12.8 & 12.8.1 – Manage Service Providers with Cardholder Data Access
Copy Link
PCI Requirement 12.8.2 - Service Providers are Responsible for the Security of Cardholder Data
Copy Link
PCI Requirement 12.8.3 – Ensure there is an Established Process for Engaging Service Providers
Copy Link
PCI Requirement 12.8.4 and 12.8.5 – Monitor Service Providers’ PCI DSS Compliance Status
Copy Link
PCI Requirement 12.9 – Service Providers are Responsible for the Security of Cardholder Data
Copy Link
PCI Requirement 2.1 - Always Change Vendor-Supplied Defaults
Copy Link
PCI Requirement 2.1.1 - Change all Wireless Vendor Defaults
Copy Link
PCI Requirement 2.2 - Develop Configuration Standards for all System Components
Copy Link
PCI Requirement 2.2.1 - Implement Only One Primary Function Per Server
Copy Link
PCI Requirement 2.2.2 - Enable Only Necessary Services, Protocols and Daemons
Copy Link
PCI Requirement 2.2.3 - Implement Additional Security Features
Copy Link
PCI Requirement 2.2.4 - Configure System Security Parameters to Prevent Misuse
Copy Link
PCI Requirement 2.2.5 - Remove all Unnecessary Functionality
Copy Link
PCI Requirement 2.3 - Encryption
Copy Link
PCI Requirement 2.4 - Maintain an Inventory of In-Scope System Components
Copy Link
PCI Requirement 2.5 - Ensure Security Policies Are Known to All Affected Parties
Copy Link
PCI Requirement 2.6 - Shared Hosting Providers Must Protect Each Entity’s Hosted Environment
Copy Link
PCI Requirement 3.1 - Keep Cardholder Data Storage to a Minimum
Copy Link
PCI Requirement 3.2 - Do Not Store Sensitive Authentication Data After Authorization
Copy Link
PCI Requirement 3.3 Mask PAN when Displayed
Copy Link
PCI Requirement 3.4 Render PAN Unreadable Anywhere it Is Stored
Copy Link
PCI Requirement 3.4.1 Logical Access Management
Copy Link
PCI Requirement 3.5 Document & Implement Procedures to Protect Keys
Copy Link
PCI Requirement 3.5.1 Maintain a Documented Description of The Cryptographic Architecture
Copy Link
PCI Requirement 3.5.2 Restrict Access to Cryptographic Keys
Copy Link
PCI Requirement 3.5.3 Store Secret and Private Keys Used to Encrypt/Decrypt Cardholder Data
Copy Link
PCI Requirement 3.5.4 Store Cryptographic Keys in The Fewest Possible Locations
Copy Link
PCI Requirement 3.6 Document & Implement all Key-Management Processes & Procedures
Copy Link
PCI Requirement 3.6.1 Generation of Strong Cryptographic Keys
Copy Link
PCI Requirement 3.6.2 Secure Cryptographic Key Distribution
Copy Link
PCI Requirement 3.6.3 Secure Cryptographic Key Storage
Copy Link
PCI Requirement 3.6.4 Cryptographic Key Changes at Cryptoperiod Completion
Copy Link
PCI Requirement 3.6.5 Replacing Weakened Keys
Copy Link
PCI Requirement 3.6.6 Using Split Knowledge & Dual Control
Copy Link
PCI Requirement 3.6.7 Prevention of Unauthorized Substitution of Cryptographic Keys
Copy Link
PCI Requirement 3.6.8 Key-Custodian Responsibilities
Copy Link
PCI Requirement 3.7 Security Policies & Operational Procedures
Copy Link
PCI Requirement 4.1 – Use Strong Cryptography & Security Protocols to Safeguard Sensitive CHD
Copy Link
PCI Requirement 4.1.1 – Ensure Wireless Network Transmitting CHD Use Strong Encryption
Copy Link
PCI Requirement 4.3 – Ensure Security Policies and Procedures are Known to all Affected Parties
Copy Link
PCI Requirement 5.1 – Deploy Anti-Virus Software on all Commonly Affected Systems
Copy Link
PCI Requirement 5.1.1 – Ensure Anti-Virus Programs Detect, Remove and Protect Against Malware
Copy Link
PCI Requirement 5.1.2 – Perform Evaluations to Identify & Evaluate Evolving Malware Threats
Copy Link
PCI Requirement 5.2 – Ensure Anti-Virus Mechanisms are Current, Perform Scans, & Generate Audit Logs
Copy Link
PCI Requirement 5.3 – Ensure Anti-Virus Mechanisms are Active and Can’t be Altered
Copy Link
PCI Requirement 5.4 – Ensure Security Policies and Procedures are Known to all Affected Parties
Copy Link
PCI Requirement 6 – Develop and Maintain Secure Systems and Applications
Copy Link
PCI Requirement 6.1 – Establish a Process to Identify Security Vulnerabilities
Copy Link
PCI Requirement 6.2 – Ensure all Systems and Software are Protected from Known Vulnerabilities
Copy Link
PCI Requirement 6.3 – Develop Secure Software Applications
Copy Link
PCI Requirement 6.3.1 – Remove Development and Test Accounts, User IDs, and Passwords Before Release
Copy Link
PCI Requirement 6.3.2 – Review Custom Code Prior to Release
Copy Link
PCI Requirement 6.4 – Follow Change Control Processes & Procedures for Changes to System Components
Copy Link
PCI Requirement 6.5 – Address Common Coding Vulnerabilities in Software-Development Processes
Copy Link
PCI Requirement 6.5.1 – 6.5.6 Recap
Copy Link
PCI Requirement 6.5.1 – Injection Flaws
Copy Link
PCI Requirement 6.5.2 – Buffer Overflow
Copy Link
PCI Requirement 6.5.3 – Insecure Cryptographic Storage
Copy Link
PCI Requirement 6.5.4 – Insecure Communications
Copy Link
PCI Requirement 6.5.5 – Improper Error Handling
Copy Link
PCI Requirement 6.5.6 – All “High Risk” Vulnerabilities
Copy Link
PCI Requirement 6.5.7 – Cross-Site Scripting (XSS)
Copy Link
PCI Requirement 6.5.8 – Improper Access Control
Copy Link
PCI Requirement 6.5.9 – Cross-Site Request Forgery
Copy Link
PCI Requirement 6.6 – Address Threats & Vulnerabilities Regularly for Public-Facing Web Applications
Copy Link
PCI Requirement 6.7 – Ensure Policies & Procedures for Systems Are Documented, in Use & Known
Copy Link
PCI Requirement 7 – Restrict Access to Cardholder Data by Business Need to Know.mp4
Copy Link
PCI Requirement 7.1 – Limit Access to System Components and Cardholder Data
Copy Link
PCI Requirement 7.1.1 – Define Access Needs for Each Role
Copy Link
PCI Requirement 7.1.2 – Restrict Access to Privileged User IDs to Least Privileges Necessary
Copy Link
PCI Requirement 7.1.3 - Assign access based on individual personnel’s job classification & function
Copy Link
PCI Requirement 7.1.4 – Require Documented Approval by Authorized Parties
Copy Link
PCI Requirement 7.2 – Establish an Access Control System
Copy Link
PCI Requirement 7.2.1 – Coverage of all System Components
Copy Link
PCI Requirement 7.2.3 – Default “Deny-All” Setting
Copy Link
PCI Requirement 7.3 – Document Policies & Procedures for Restricting Access to Cardholder Data
Copy Link
PCI Requirement 8 - Identify and Authenticate Access to System Components
Copy Link
PCI Requirement 8.1 – Define and Implement Policies and Procedures to Ensure Proper User Management
Copy Link
PCI Requirement 8.1.2 – Control Addition, Deletion, and Modification of User IDs, Credentials
Copy Link
PCI Requirement 8.1.3 – Immediately Revoke Access for Terminated Users
Copy Link
PCI Requirement 8.1.4 – RemoveDisable Inactive User Accounts Within 90 Days
Copy Link
PCI Requirement 8.1.5 – Manage IDs Used by 3rd Parties to Access, Support, or Maintain System Comps
Copy Link
PCI Requirement 8.1.6 – Limit Repeated Access Attempts by Locking Out User ID After Six Attempts
Copy Link
PCI Requirement 8.1.7 – Set Lockout Duration to a Minimum of 30 Minutes
Copy Link
PCI Requirement 8.1.8 – Require Re-Authentication After 15 Minutes of Inactivity
Copy Link
PCI Requirement 8.2 – Ensure Proper User-Authentication Management by Something You Know
Copy Link
PCI Requirement 8.2.1 – Use Strong Cryptography to Render All Authentication Credentials Unreadable
Copy Link
PCI Requirement 8.2.3 – Passwords Require a Min. of Seven Characters and Contain Numbers & Letters
Copy Link
PCI Requirement 8.2.4 – Change User PasswordsPassphrases at Least Once Every 90 Days
Copy Link
PCI Requirement 8.2.5 – New Passwords Can’t Be the Same as Any of the Last Four Passwords Used
Copy Link
PCI Requirement 8.2.6 – Set Passwords for First-Time Use and Upon Reset to a Unique Value
Copy Link
PCI Requirement 8.3 – Secure All Individual Non-Console Administrative Access
Copy Link
PCI Requirement 8.3.1 – Incorporate Multi-Factor Authentication for All Non-Console Access
Copy Link
PCI Requirement 8.3.2 – Incorporate Multi-Factor Authentication for all Remote Network Access
Copy Link
PCI Requirement 8.4 – Document and Communicate Authentication Policies and Procedures to All Users
Copy Link
PCI Requirement 8.5 – Do Not Use Group, Shared, or Generic IDs, or Passwords
Copy Link
PCI Requirement 8.5.1 – Remote Access to Customer Premises Must Use Unique Authentication
Copy Link
PCI Requirement 8.6 – Authentication Mechanisms Must Not Be Shared Among Multiple Accounts
Copy Link
PCI Requirement 8.7 – Restrict All Access to Any Database Containing Cardholder Data
Copy Link
PCI Requirement 8.8 – Ensure Policies & Procedures for Authentication are Documented
Copy Link
PCI Requirement 9 – Restrict Physical Access to Cardholder Data.mp4
Copy Link
PCI Requirement 9.1 – Use Facility Entry Controls to Limit Physical Access to CDE
Copy Link
PCI Requirement 9.1.1 – Use Video Cameras or Access Control Mechanisms to Monitor Physical Access
Copy Link
PCI Requirement 9.1.2 – Implement Physical Controls to Restrict Access to Accessible Network Jacks
Copy Link
PCI Requirement 9.1.3 – Restrict Physical Access to Wireless Access Points
Copy Link
PCI Requirement 9.10 – Ensure Policies for Restricting Physical Access to Cardholder Data are Known
Copy Link
PCI Requirement 9.2 – Develop Procedures to Easily Distinguish Between Onsite Personnel and Visitors
Copy Link
PCI Requirement 9.3 – Control Physical Access for Onsite Personnel to Sensitive Areas
Copy Link
PCI Requirement 9.4 – Implement Procedures to Identify and Authorize Visitors
Copy Link
PCI Requirement 9.4.1 – Visitors are Authorized Before Entering, and Escorted at all Times
Copy Link
PCI Requirement 9.4.2 – Visitors are Identified and Given a Badge that Expires
Copy Link
PCI Requirement 9.4.3 – Visitors are Asked to Surrender the Badge Before Leaving the Facility
Copy Link
PCI Requirement 9.4.4 – A Visitor Log is Used to Maintain a Physical Audit Trail of Visitor Activity
Copy Link
PCI Requirement 9.5 – Physically Secure all Media
Copy Link
PCI Requirement 9.5.1 – Store Media Backups in a Secure Location and Review the Location’s Security
Copy Link
PCI Requirement 9.6 – Maintain Control Over the InternalExternal Distribution of Any Kind of Media
Copy Link
PCI Requirement 9.6.1 – Classify Media so the Sensitivity of the Data Can Be Determined
Copy Link
PCI Requirement 9.6.2 – Send the Media by Secured Courier
Copy Link
PCI Requirement 9.6.3 – Ensure Management Approves All Media Moved from a Secured Area