Information Security Policy | Establish Policy to Disconnect Vendor Sessions When Not in Use | KirkpatrickPrice

Establish Policy to Disconnect Vendor Sessions When Not in Use

Related Videos

10.6.1 – Review Daily All Security Events and Logs of All System Components.mp4

10.6.2 – Review Logs of All Other System Components Based Policies and Risk Management Strategy

10.6.3 –Follow Up Exceptions and Anomalies Identified During the Review Process

Activate Azure Key Rotation Reminders.mov

Allow Azure Services Access to Storage Accounts

Configure Shared Access Security Tokens to Expire within an Hour

Create Policies for Usage of Critical Technologies

Create a Review Process of Guest Users

Define Staff Information Security Responsibilities in Policy

Disable Caching of Second Factor of Authentication Beyond One Day

Disable Public Access Level for Storage Accounts with Blob Containers

Distribute Policies to Affected Parties

Do Not Allow Users to Remember MFA on Devices They Trust

Enable Logging of Read, Write, and Delete Requests for Blob Service

Enable Logging of Read, Write, and Delete Requests for Table Service

Enable Multifactor Authentication for Administrators

Enable Queue Storage Logging for Read Write Access

Encrypt Infrastructure to Further Protect Your Environment

Enforce Multifactor Authentication for All Users

Ensure Notifications are Enabled for Password Resets

Ensure Only Authorized Users Can Create Security Groups

Ensure Soft Delete Is Enabled

Ensure the Minimum TLS Version for Storage Accounts Is Set to 1.2

Establish Policy to Disconnect Remote Sessions

Establish a Policy to Manage Your Service Providers

Establishing the Scope of your Cardholder Data Environment

Evaluate Public IP Addresses Regularly

Evaluate and Restrict UDP Access from the Internet

Greg Halpin Audit Tip

How to Disseminate an Information Security Policy

Introduction to PCI DSS Requirement 1

Introduction to PCI DSS: What is the Payment Card Industry Data Security Standard

Introduction to PCI Requirement 2.mp4

Monitor Your Environment with Network Watcher

Notify Admins of Other Admin Password Resets

Only Allow Administrators to Delete Locked Resources

Only Allow Approved Employees to Invite Guests

PCI DSS Requirement 1.1.1 - Implementing a Change Control Program

PCI DSS Requirement 1.1.2 and 1.1.3 - Network Documentation Best Practices

PCI DSS Requirement 1.1.4 - Establishing a Firewall and DMZ

PCI DSS Requirement 1.1.5 Defining Roles and Responsibilities for Managing Network Components

PCI DSS Requirement 1.1.6 Documentation of Business Justification & Approval for use of all Services, Ports and Protocols

PCI DSS Requirement 1.1.7 - Review Firewall and Router Rule Sets

PCI DSS Requirement 1.2 Restrict Connections to Untrusted Networks

PCI DSS Requirement 1.2.1 Restrict Traffic to that which is Necessary

PCI DSS Requirement 1.2.2 Secure and Synchronize Router Configuration Files

PCI DSS Requirement 1.2.3 Install Firewalls Between all Wireless Networks and the CDE

PCI DSS Requirement 1.3 Examine Firewall and Router Configurations

PCI DSS Requirement 1.3.1 - Establishing a DMZ

PCI DSS Requirement 1.3.2 Limit Inbound Internet Traffic

PCI DSS Requirement 1.3.3 - Implement Anti Spoofing Measures

PCI DSS Requirement 1.3.4 - Deny Unauthorized Outbound Traffic

PCI DSS Requirement 1.3.5 - Permit Only Established Connections into the Network

PCI DSS Requirement 1.3.6 Segregate the CDE from the DMZ

PCI DSS Requirement 1.3.7 Do Not Disclose Private IP Addresses

PCI DSS Requirement 1.4 Install Personal Firewall Software

PCI DSS Requirement 1.5 Ensure Security Policies are Known to all Affected Parties

PCI Requirement 10 – Track and Monitor all Access to Network Resources and Cardholder Data

PCI Requirement 10.1 – Implement Audit Trails to Link all Access to System Components

PCI Requirement 10.2 – Implement Automated Audit Trails for all System Components

PCI Requirement 10.2.1 – All Individual User Accesses to Cardholder Data

PCI Requirement 10.2.2 – All Actions Taken by Any Individual with Root or Administrative Privileges

PCI Requirement 10.2.3 – Access to All Audit Trails

PCI Requirement 10.2.4 – Invalid Logical Access Attempts.mp4

PCI Requirement 10.2.5 – Use of and Changes to Identification Accounts with Root Privileges

PCI Requirement 10.2.6 – Initialization, Stopping, or Pausing of the Audit Logs

PCI Requirement 10.2.7 – Creation and Deletion of System-Level Objects

PCI Requirement 10.3 – Record at Least the Following Audit Trail Entries for All System Components

PCI Requirement 10.3.1 – User Identification

PCI Requirement 10.3.2 – Type of Event

PCI Requirement 10.3.3 – Date and Time

PCI Requirement 10.3.4 – Success or Failure Indication

PCI Requirement 10.3.5 – Origination of Event

PCI Requirement 10.3.6 – Identity or Name of Affected Data, System Component, or Resource

PCI Requirement 10.4 – Using Time-Synchronization Technology, Synchronize All Critical Systems

PCI Requirement 10.4.1 – Critical Systems Have the Correct and Consistent Time

PCI Requirement 10.4.2 – Time Data is Protected

PCI Requirement 10.4.3 – Time Settings Are Received from Industry-Accepted Time Sources

PCI Requirement 10.5 – Secure Audit Trails so They Cannot Be Altered

PCI Requirement 10.5.1 – Limit Viewing of Audit Trails to Those with a Job-Related Need

PCI Requirement 10.5.2 – Protect Audit Trail Files from Unauthorized Modifications

PCI Requirement 10.5.3 – Promptly Back Up Audit Trail Files to a Centralized Log Server

PCI Requirement 10.5.4 – Write Logs for External-Facing Technologies onto a Secure Device

PCI Requirement 10.5.5 – Use File-Integrity Monitoring or Change-Detection Software on Logs

PCI Requirement 10.6 – Review Logs and Security Events for All System Components

PCI Requirement 10.7 – Retain Audit Trail History for at Least One Year, with Three Months Available

PCI Requirement 10.8 –Implement a Process for the Detection of Failures of Critical Control Systems

PCI Requirement 10.8.1 –Respond to Failures of Any Critical Security Controls in a Timely Manner

PCI Requirement 10.9 – Document Policies & Procedures for Monitoring Access to Network Resources

PCI Requirement 11 - Regularly Test Security Systems & Processes

PCI Requirement 11.1 – Implement Processes to Test for the Presence of Wireless Access Points

PCI Requirement 11.1.2 – Unauthorized Wireless Access Points Detection

PCI Requirement 11.2 – Quarterly Internal & External Vulnerability Scans

PCI Requirement 11.2.1 – Perform Quarterly Internal Vulnerability Scans

PCI Requirement 11.2.2 – Perform Quarterly External Vulnerability Scans

PCI Requirement 11.2.3 – Perform Internal and External Scans and Rescans as Needed

PCI Requirement 11.3 – Implement a Methodology for Penetration Testing

PCI Requirement 11.3.1 – Perform External Penetration Testing at Least Annually

PCI Requirement 11.3.2 – Perform Internal Penetration Testing at Least Annually

PCI Requirement 11.3.3 – Exploitable Vulnerabilities Found During Penetration Testing are Corrected

PCI Requirement 11.3.4 – Perform Penetration Tests if Segmentation is Used

PCI Requirement 11.3.4.1 – Confirm PCI DSS Scope by Performing Penetration Testing on Segmentation

PCI Requirement 11.4 – Use Intrusion-Detection and/or Intrusion-Prevention Techniques

PCI Requirement 11.5 – Deploy a Change-Detection Mechanisms to Alert Personnel

PCI Requirement 11.5.1 – Implement a Process to Respond to Change-Detection Solution Alerts

PCI Requirement 11.6 – Ensure Security Policies for Security Monitoring are Documented

PCI Requirement 12- Maintain a Policy that Addresses Information Security for All Personnel

PCI Requirement 12.1 & 12.1.1 – Establish, Publish, Maintain, and Disseminate a Security Policy

PCI Requirement 12.10 – Implement an Incident Response Plan

PCI Requirement 12.10.1 – Create the Incident Response Plan to Be Implemented

PCI Requirement 12.10.2 – Review and Test the Plan at Least Annually

PCI Requirement 12.10.3 – Designate Specific Personnel to Be Available on a 24/7 Basis

PCI Requirement 12.10.4 – Provide Training to Staff with Security Breach Responsibilities

PCI Requirement 12.10.5 – Include Alerts from Security Monitoring Systems

PCI Requirement 12.10.6 – Develop a Process to Modify and Evolve the Incident Response Plan

PCI Requirement 12.11 – Perform Reviews to Confirm Personnel Are Following Security Policies

PCI Requirement 12.11.1 – Maintain Documentation of Quarterly Review Process

PCI Requirement 12.2 – Implement a Risk Assessment Process

PCI Requirement 12.3 – Develop Usage Policies for Critical Technologies

PCI Requirement 12.3.1 – Explicit Approval by Authorized Parties

PCI Requirement 12.3.10 – Prohibit the Moving of Cardholder Data onto Local Hard Drives

PCI Requirement 12.3.2 – Authentication for Use of the Technology

PCI Requirement 12.3.3 – A List of All Such Devices and Personnel with Access

PCI Requirement 12.3.4 – A Method to Accurately Determine Owner, Contact Information, and Purpose

PCI Requirement 12.3.5 – Acceptable Uses of the Technology

PCI Requirement 12.3.6 – Acceptable Network Locations for the Technologies

PCI Requirement 12.3.7 – List of Company-Approved Products

PCI Requirement 12.3.8 – Automatic Disconnect of Sessions for Remote-Access Technologies

PCI Requirement 12.3.9 – Activation of Remote-Access Technologies for Vendors and Business Partners

PCI Requirement 12.4 – Ensure Security Policies & Procedures Define Responsibilities for All

PCI Requirement 12.4.1 – Executive Management Shall Establish Responsibility

PCI Requirement 12.5 – Assign Information Security Management Responsibilities to a Team

PCI Requirement 12.5.1 – Establish, Document, and Distribute Security Policies and Procedures

PCI Requirement 12.5.2 – Monitor and Analyze Security Alerts and Distribute to Appropriate Personnel

PCI Requirement 12.5.3 – Establish Security Incident Response and Escalation Procedures

PCI Requirement 12.5.4 – Administer User Accounts, Including Additions, Deletions, and Modifications

PCI Requirement 12.5.5 – Monitor and Control All Access to Data

PCI Requirement 12.6 – Implement a Formal Security Awareness Program

PCI Requirement 12.6.1 – Educate Personnel Upon Hire and at Least Annually

PCI Requirement 12.6.2 – Require Personnel to Read and Understand Security Policies and Procedures

PCI Requirement 12.7 – Screen Personnel Prior to Hire to Minimize the Risk of Attacks

PCI Requirement 12.8 & 12.8.1 – Manage Service Providers with Cardholder Data Access

PCI Requirement 12.8.2 - Service Providers are Responsible for the Security of Cardholder Data

PCI Requirement 12.8.3 – Ensure there is an Established Process for Engaging Service Providers

PCI Requirement 12.8.4 and 12.8.5 – Monitor Service Providers’ PCI DSS Compliance Status

PCI Requirement 12.9 – Service Providers are Responsible for the Security of Cardholder Data

PCI Requirement 2.1 - Always Change Vendor-Supplied Defaults

PCI Requirement 2.1.1 - Change all Wireless Vendor Defaults

PCI Requirement 2.2 - Develop Configuration Standards for all System Components

PCI Requirement 2.2.1 - Implement Only One Primary Function Per Server

PCI Requirement 2.2.2 - Enable Only Necessary Services, Protocols and Daemons

PCI Requirement 2.2.3 - Implement Additional Security Features

PCI Requirement 2.2.4 - Configure System Security Parameters to Prevent Misuse

PCI Requirement 2.2.5 - Remove all Unnecessary Functionality

PCI Requirement 2.3 - Encryption

PCI Requirement 2.4 - Maintain an Inventory of In-Scope System Components

PCI Requirement 2.5 - Ensure Security Policies Are Known to All Affected Parties

PCI Requirement 2.6 - Shared Hosting Providers Must Protect Each Entity’s Hosted Environment

PCI Requirement 3.1 - Keep Cardholder Data Storage to a Minimum

PCI Requirement 3.2 - Do Not Store Sensitive Authentication Data After Authorization

PCI Requirement 3.3 Mask PAN when Displayed

PCI Requirement 3.4 Render PAN Unreadable Anywhere it Is Stored

PCI Requirement 3.4.1 Logical Access Management

PCI Requirement 3.5 Document & Implement Procedures to Protect Keys

PCI Requirement 3.5.1 Maintain a Documented Description of The Cryptographic Architecture

PCI Requirement 3.5.2 Restrict Access to Cryptographic Keys

PCI Requirement 3.5.3 Store Secret and Private Keys Used to Encrypt/Decrypt Cardholder Data

PCI Requirement 3.5.4 Store Cryptographic Keys in The Fewest Possible Locations

PCI Requirement 3.6 Document & Implement all Key-Management Processes & Procedures

PCI Requirement 3.6.1 Generation of Strong Cryptographic Keys

PCI Requirement 3.6.2 Secure Cryptographic Key Distribution

PCI Requirement 3.6.3 Secure Cryptographic Key Storage

PCI Requirement 3.6.4 Cryptographic Key Changes at Cryptoperiod Completion

PCI Requirement 3.6.5 Replacing Weakened Keys

PCI Requirement 3.6.6 Using Split Knowledge & Dual Control

PCI Requirement 3.6.7 Prevention of Unauthorized Substitution of Cryptographic Keys

PCI Requirement 3.6.8 Key-Custodian Responsibilities

PCI Requirement 3.7 Security Policies & Operational Procedures

PCI Requirement 4.1 – Use Strong Cryptography & Security Protocols to Safeguard Sensitive CHD

PCI Requirement 4.1.1 – Ensure Wireless Network Transmitting CHD Use Strong Encryption

PCI Requirement 4.3 – Ensure Security Policies and Procedures are Known to all Affected Parties

PCI Requirement 5.1 – Deploy Anti-Virus Software on all Commonly Affected Systems

PCI Requirement 5.1.1 – Ensure Anti-Virus Programs Detect, Remove and Protect Against Malware

PCI Requirement 5.1.2 – Perform Evaluations to Identify & Evaluate Evolving Malware Threats

PCI Requirement 5.2 – Ensure Anti-Virus Mechanisms are Current, Perform Scans, & Generate Audit Logs

PCI Requirement 5.3 – Ensure Anti-Virus Mechanisms are Active and Can’t be Altered

PCI Requirement 5.4 – Ensure Security Policies and Procedures are Known to all Affected Parties

PCI Requirement 6 – Develop and Maintain Secure Systems and Applications

PCI Requirement 6.1 – Establish a Process to Identify Security Vulnerabilities

PCI Requirement 6.2 – Ensure all Systems and Software are Protected from Known Vulnerabilities

PCI Requirement 6.3 – Develop Secure Software Applications

PCI Requirement 6.3.1 – Remove Development and Test Accounts, User IDs, and Passwords Before Release

PCI Requirement 6.3.2 – Review Custom Code Prior to Release

PCI Requirement 6.4 – Follow Change Control Processes & Procedures for Changes to System Components

PCI Requirement 6.5 – Address Common Coding Vulnerabilities in Software-Development Processes

PCI Requirement 6.5.1 – 6.5.6 Recap

PCI Requirement 6.5.1 – Injection Flaws

PCI Requirement 6.5.2 – Buffer Overflow

PCI Requirement 6.5.3 – Insecure Cryptographic Storage

PCI Requirement 6.5.4 – Insecure Communications

PCI Requirement 6.5.5 – Improper Error Handling

PCI Requirement 6.5.6 – All “High Risk” Vulnerabilities

PCI Requirement 6.5.7 – Cross-Site Scripting (XSS)

PCI Requirement 6.5.8 – Improper Access Control

PCI Requirement 6.5.9 – Cross-Site Request Forgery

PCI Requirement 6.6 – Address Threats & Vulnerabilities Regularly for Public-Facing Web Applications

PCI Requirement 6.7 – Ensure Policies & Procedures for Systems Are Documented, in Use & Known

PCI Requirement 7 – Restrict Access to Cardholder Data by Business Need to Know.mp4

PCI Requirement 7.1 – Limit Access to System Components and Cardholder Data

PCI Requirement 7.1.1 – Define Access Needs for Each Role

PCI Requirement 7.1.2 – Restrict Access to Privileged User IDs to Least Privileges Necessary

PCI Requirement 7.1.3 - Assign access based on individual personnel’s job classification & function

PCI Requirement 7.1.4 – Require Documented Approval by Authorized Parties

PCI Requirement 7.2 – Establish an Access Control System

PCI Requirement 7.2.1 – Coverage of all System Components

PCI Requirement 7.2.2 – Assignment of Privileges Based on Job Function

PCI Requirement 7.2.3 – Default “Deny-All” Setting

PCI Requirement 7.3 – Document Policies & Procedures for Restricting Access to Cardholder Data

PCI Requirement 8 - Identify and Authenticate Access to System Components

PCI Requirement 8.1 – Define and Implement Policies and Procedures to Ensure Proper User Management

PCI Requirement 8.1.2 – Control Addition, Deletion, and Modification of User IDs, Credentials

PCI Requirement 8.1.3 – Immediately Revoke Access for Terminated Users

PCI Requirement 8.1.4 – RemoveDisable Inactive User Accounts Within 90 Days

PCI Requirement 8.1.5 – Manage IDs Used by 3rd Parties to Access, Support, or Maintain System Comps

PCI Requirement 8.1.6 – Limit Repeated Access Attempts by Locking Out User ID After Six Attempts

PCI Requirement 8.1.7 – Set Lockout Duration to a Minimum of 30 Minutes

PCI Requirement 8.1.8 – Require Re-Authentication After 15 Minutes of Inactivity

PCI Requirement 8.2 – Ensure Proper User-Authentication Management by Something You Know

PCI Requirement 8.2.1 – Use Strong Cryptography to Render All Authentication Credentials Unreadable

PCI Requirement 8.2.3 – Passwords Require a Min. of Seven Characters and Contain Numbers & Letters

PCI Requirement 8.2.4 – Change User PasswordsPassphrases at Least Once Every 90 Days

PCI Requirement 8.2.5 – New Passwords Can’t Be the Same as Any of the Last Four Passwords Used

PCI Requirement 8.2.6 – Set Passwords for First-Time Use and Upon Reset to a Unique Value

PCI Requirement 8.3 – Secure All Individual Non-Console Administrative Access

PCI Requirement 8.3.1 – Incorporate Multi-Factor Authentication for All Non-Console Access

PCI Requirement 8.3.2 – Incorporate Multi-Factor Authentication for all Remote Network Access

PCI Requirement 8.4 – Document and Communicate Authentication Policies and Procedures to All Users

PCI Requirement 8.5 – Do Not Use Group, Shared, or Generic IDs, or Passwords

PCI Requirement 8.5.1 – Remote Access to Customer Premises Must Use Unique Authentication

PCI Requirement 8.6 – Authentication Mechanisms Must Not Be Shared Among Multiple Accounts

PCI Requirement 8.7 – Restrict All Access to Any Database Containing Cardholder Data

PCI Requirement 8.8 – Ensure Policies & Procedures for Authentication are Documented

PCI Requirement 9 – Restrict Physical Access to Cardholder Data.mp4

PCI Requirement 9.1 – Use Facility Entry Controls to Limit Physical Access to CDE

PCI Requirement 9.1.1 – Use Video Cameras or Access Control Mechanisms to Monitor Physical Access

PCI Requirement 9.1.2 – Implement Physical Controls to Restrict Access to Accessible Network Jacks

PCI Requirement 9.1.3 – Restrict Physical Access to Wireless Access Points

PCI Requirement 9.10 – Ensure Policies for Restricting Physical Access to Cardholder Data are Known

PCI Requirement 9.2 – Develop Procedures to Easily Distinguish Between Onsite Personnel and Visitors

PCI Requirement 9.3 – Control Physical Access for Onsite Personnel to Sensitive Areas

PCI Requirement 9.4 – Implement Procedures to Identify and Authorize Visitors

PCI Requirement 9.4.1 – Visitors are Authorized Before Entering, and Escorted at all Times

PCI Requirement 9.4.2 – Visitors are Identified and Given a Badge that Expires

PCI Requirement 9.4.3 – Visitors are Asked to Surrender the Badge Before Leaving the Facility

PCI Requirement 9.4.4 – A Visitor Log is Used to Maintain a Physical Audit Trail of Visitor Activity

PCI Requirement 9.5 – Physically Secure all Media

PCI Requirement 9.5.1 – Store Media Backups in a Secure Location and Review the Location’s Security

PCI Requirement 9.6 – Maintain Control Over the InternalExternal Distribution of Any Kind of Media

PCI Requirement 9.6.1 – Classify Media so the Sensitivity of the Data Can Be Determined

PCI Requirement 9.6.2 – Send the Media by Secured Courier

PCI Requirement 9.6.3 – Ensure Management Approves All Media Moved from a Secured Area

PCI Requirement 9.7 – Maintain Strict Control Over the Storage and Accessibility of Media

PCI Requirement 9.7.1 – Properly Maintain Inventory Logs of All Media

PCI Requirement 9.8 – Destroy Media When it is no Longer Needed

PCI Requirement 9.8.1 – Shred Hard-Copy Materials so CHD Cannot be Reconstructed

PCI Requirement 9.8.2 – Render CHD on Electronic Media Unrecoverable

PCI Requirement 9.9 – Protect Devices That Capture Payment Card Data via Direct Physical Interaction

PCI Requirement 9.9.1 – Maintain an Up-To-Date List of Devices

PCI Requirement 9.9.2 – Periodically Inspect Device Surfaces to Detect Tampering or Substitution

PCI Requirement 9.9.3 – Provide Training for Personnel to Be Aware of Attempted Tampering of Devices

PCI Requirements 3.2.1, 3.2.2, & 3.2.3 Do Not Store Tracks, Codes, or PINs After Authorization

PCI v3.2.1 vs. PCI 4.0: What's Changed?

PCI v4.0 - 12.1.1: Have and Utilize an Information Security Policy

PCI v4.0 - 12.1.2: Review and Update Your Information Security Policy Regularly

PCI v4.0 - 12.1.3: Ensure Your Information Security Policy Defines Roles and Responsibilities

PCI v4.0 - 12.1.4: Formally Assign Information Security Responsibility to a CISO

PCI v4.0 - 12.10.1: Establish a Comprehensive Incident Response Plan

PCI v4.0 - 12.10.2: Regularly Review the Incident Response Plan

PCI v4.0 - 12.10.3: Ensure Specific Security Personnel Are Available for Incident Response

PCI v4.0 - 12.10.4.1: Utilize the Targeted Risk Analysis to Determine Incident Response Training Frequency

PCI v4.0 - 12.10.4: Appropriately Train Incident Response Personnel

PCI v4.0 - 12.10.5: Include Monitoring and Responding to Alerts in the Incident Response Plan

PCI v4.0 - 12.10.6: Modify the Incident Response Plan as Needed

PCI v4.0 - 12.10.7: Implement Incident Response Procedures Upon Detection of Stored Primary Account Numbers

PCI v4.0 - 12.2.1: Acceptable Use Policies Are Documented and Implemented

PCI v4.0 - 12.3.1: Use Targeted Risk Analyses to Support Flexible Testing

PCI v4.0 - 12.3.2: Perform Targeted Risk Analyses for Customized Approach

PCI v4.0 - 12.3.3: Document and Review Cryptographic Cipher Suites and Protocols in Use

PCI v4.0 - 12.3.4: Review Software and Hardware Technologies

PCI v4.0 - 12.4.1: Service Providers Must Establish Protections for Card Holder Data

PCI v4.0 - 12.4.2.1: Document the Reviews Performed in Requirement 12.4.2

PCI v4.0 - 12.4.2: Ensure Personnel Are Performing Their Duties

PCI v4.0 - 12.5.1: Maintain an Inventory of System Components That Are in Scope

PCI v4.0 - 12.5.2.1: Service Providers Must Document and Confirm Scope Frequently

PCI v4.0 - 12.5.2: Document and Confirm Scope Regularly

PCI v4.0 - 12.5.3: Review Scope After Significant Changes to Organizational Structure

PCI v4.0 - 12.6.1: Implement Formal Security Awareness Training

PCI v4.0 - 12.6.2: Review Your Information Security Awareness Program Regularly

PCI v4.0 - 12.6.3.1: Include Specific Threats and Vulnerabilities in Information Security Awareness Trainings

PCI v4.0 - 12.6.3.2: Include Acceptable Use Policies in Security Awareness Trainings

PCI v4.0 - 12.6.3: Hold Information Security Awareness Trainings Regularly

PCI v4.0 - 12.7.1: Screen Personnel Who Have Access to the Cardholder Data Environment

PCI v4.0 - 12.8.1: Keep Record of Third-Party Service Providers that Account Data Is Shared With

PCI v4.0 - 12.8.2: Maintain Written Requirements with Third-Party Service Providers

PCI v4.0 - 12.8.3: Establish a Process for Engaging with Third-Party Service Providers

PCI v4.0 - 12.8.4: Monitor the PCI DSS Compliance of Third-Party Service Providers

PCI v4.0 - 12.8.5: Detail Responsibilities Held by Third-Party Service Providers

PCI v4.0 - 12.9.1: Acknowledge Account Security Responsibilities

PCI v4.0 - 12.9.2: Provide Compliance Information to Clients Upon Request

PCI v4.0 - 5.1.1: Have Requirement 5 Policies and Procedures In Place

PCI v4.0 - 5.1.2: Have Requirement 5 Roles and Responsibilities In Place

PCI v4.0 - 5.2.1: Deploy Anti-Malware Solutions on All System Components

PCI v4.0 - 5.2.2: Utilize Sufficient Anti-Malware Solutions

PCI v4.0 - 5.2.3.1: Define Frequency of Periodic Evaluations of Systems in the Targeted Risk Analysis

PCI v4.0 - 5.2.3: Periodically Review Systems Not Protected by Anti-Malware Solutions

PCI v4.0 - 5.3.1: Keep Anti-Malware Solutions Up to Date

PCI v4.0 - 5.3.2.1: Define Frequency of Anti-Malware Scans in Targeted Risk Analysis

PCI v4.0 - 5.3.2: Ensure Anti-Malware Solution Performs Scans or Continuous Behavior Analyses

PCI v4.0 - 5.3.3: Utilize Anti-Malware Solutions for Removable Media

PCI v4.0 - 5.3.4: Enable and Retain Audit Logs for Anti-Malware Solutions

PCI v4.0 - 5.3.5: Do Not Allow Anti-Malware Solutions to Be Altered or Disabled

PCI v4.0 - 5.4.1: Have Protections in Place to Prevent Phishing Attacks

Periodically Regenerate Access Keys

Policies, Procedures, and Standards - Best Practices for PCI DSS Compliance

Policy to Prohibit Cardholder Data on Remote Technology

Prevent Bad Passwords in Azure

Protect Against Malicious Attacks with Azure AD MFA

Protect Cardholder Data Over the Internet

Quarterly Reviews of Your Security Program

Require 2 Ways of Authentication for Resetting Passwords

Require Multifactor Authentication for Administrators

Requirement 4 - Encrypt Transmission of Cardholder Data Across Open, Public Networks

Requirement 4.2 – Never Send Unprotected PAN by End-User Technologies

Restrict Access to Azure Active Directory (ADD)

Restrict Access to Azure Storage From All Networks

Restrict Access to Create Security Groups Only to Administrators

Restrict Users from Adding Apps

Restrict and Review SSH Access from the Internet

Restrict and Secure Your Azure Environment

Review and Restrict RDP Access from the Internet

Risky Sign-Ins: What They Are and How to Prevent Them

Screen Employees to Reduce Risk

Service Providers to Establish Charters for Information Security Program

Set Expectations for Daily and Quarterly Reviews in Your Policy

The 12 PCI DSS Requirements - How to Ensure PCI Compliance

The Importance of Following a Remote Access Policy

The Importance of Publishing an Information Security Policy

The Importance of Responsibility Acknowledgement from Service Providers

Update Your Policy When Your Environment Changes

Utilize Flow Logs to Log Traffic in Your Environment

Utilize Private Endpoints to Access Storage Accounts

Verify Only Administrators Manage Group Membership Access

What to Include in a List of Service Providers

What to Include in a Written Contract with Service Providers