Security Policy

Security Policy


This document is the property of GRANITE GOLD SERVICES; it contains information that is proprietary, confidential, or otherwise restricted from disclosure. If you are not an authorized recipient, please return this document to the above-named owner. Dissemination, distribution, copying or use of this document in whole or in part by anyone other than the intended recipient is strictly prohibited without prior written permission of GRANITE GOLD SERVICES.

Introduction and Scope


This document explains GRANITE GOLD SERVICES’s credit card security requirements as required by the Payment Card Industry Data Security Standard (PCI DSS) Program.  GRANITE GOLD SERVICES management is committed to these security policies to protect information utilized by GRANITE GOLD SERVICES in attaining its business goals.  All employees are required to adhere to the policies described within this document.

Scope of Compliance

The PCI requirements apply to all systems that store, process, or transmit cardholder data.  Currently, GRANITE GOLD SERVICES’s cardholder environment consists only of limited payment applications (typically point-of-sale systems) connected to the internet, but does not include storage of cardholder data on any computer system.

Due to the limited nature of the in-scope environment, this document is intended to meet the PCI requirements as defined in Self-Assessment Questionnaire (SAQ) A-EP, ver. 3.0, released February, 2014.  Should GRANITE GOLD SERVICES implement additional acceptance channels, begin storing cardholder data in electronic format, or otherwise become ineligible to validate compliance under SAQ A-EP, it will be the responsibility of GRANITE GOLD SERVICES to determine the appropriate compliance criteria and implement additional policies and controls as needed.

Requirement 1:  Build and Maintain a Secure Network

Network Description

GRANITE GOLD SERVICES’s network will be configured with a requirement for a firewall at each Internet connection and between the internet-facing demilitarized zone (DMZ) containing the in-scope web server and the internal network zone that contains systems not directly involved in the payment process. (PCI Requirement 1.1.4)

The network administrator shall maintain documentation which details use of all services, protocols, and ports allowed into the internal network zone. This list will include business justification for any traffic allowed in or out of the network. It will also include documentation of security features implemented for those protocols considered to be insecure. Examples of insecure services, protocols, or ports include but are not limited to FTP, Telnet, POP3, IMAP, and SNMP v1 and v2. (PCI Requirement 1.1.6)

Firewall Configuration

Firewalls must restrict connections between untrusted networks and any system in the cardholder data environment.  An “untrusted network” is any network that is external to the networks belonging to the entity under review, and/or which is out of the entity’s ability to control or manage. Access to the internet must be through a firewall, as must any direct connection to a vendor, processor, or service provider.(PCI Requirement 1.2)

Inbound and outbound traffic must be restricted by the firewalls to that which is necessary for the cardholder data environment.  All other inbound and outbound traffic must be specifically denied. (PCI Requirement 1.2.1)

Firewall configuration must prohibit direct public access between the Internet and any system component in the cardholder data environment as follows:

  • Outbound traffic from the cardholder data environment to the Internet must be explicitly authorized by management and controlled by the firewall. (PCI Requirement 1.3.5)
  • Firewalls used to protect the cardholder data environment must implement stateful inspection, also known as dynamic packet filtering. (PCI Requirement 1.3.6)
  • Use network techniques (such as NAT or RFC 1918 addressing) so as to not disclose private IP addresses and routing information to unauthorized parties.

Requirement 2:  Do not use Vendor-Supplied Defaults for System Passwords and Other Security Parameters

Vendor Defaults

Vendor-supplied defaults must always be changed before installing a system on the network.  Examples of vendor-defaults include passwords, SNMP community strings, and elimination of unnecessary accounts. (PCI Requirement 2.1)

Configuration Standards for Systems

Configuration standards for all system components must be developed and enforced. GRANITE GOLD SERVICES must insure that these standards address all known security vulnerabilities and are consistent with industry-accepted system hardening standards. (PCI Requirement 2.2)

Configuration standards must be updated as new vulnerability issues are identified, and they must be enforced on any new systems before they are added to the cardholder data environment. The standards must cover the following:

  • Changing of all vendor-supplied defaults and elimination of unnecessary default accounts.
  • Implementing only one primary function per server to prevent functions that require different security levels from co-existing on the same server. (PCI Requirement 2.2.1)
  • Enabling only necessary services, protocols, daemons, etc., as required for the function of the system. (PCI Requirement 2.2.2)
  • Implementing additional security features for any required services, protocols or daemons that are considered to be insecure. (PCI Requirement 2.2.3)
  • Configuring system security parameters to prevent misuse
  • Removing all unnecessary functionality, such as scripts, drivers, features, subsystems, file systems, and unnecessary web servers. (PCI Requirement 2.2.5)

System administrators and any other personnel that configure system components must be knowledgeable about common security parameter settings for those system components. They must also be responsible to insure that security parameter settings set appropriately on all system components before they enter production. (PCI Requirement 2.2.4)

Non-Console Administrative Access

Credentials for non-console administrative access must be encrypted using technologies such as SSH, VPN, or SSL/TLS. Encryption technologies must include the following: (PCI Requirement 2.3)

  • Must use strong cryptography, and the encryption method must be invoked before the administrator’s password is requested.
  • System services and parameter files must be configured to prevent the use of telnet and other insecure remote login commands.
  • Must include administrator access to web-based management interfaces.
  • Use vendor documentation and knowledge of personnel to verify that strong cryptography is in use for all non-console access and that for the technology in use it is implemented according to industry best practices and vendor recommendations.

Requirement 3:  Protect Stored Cardholder Data

Prohibited Data

Processes must be in place to securely delete sensitive authentication data (defined below) post-authorization so that the data is unrecoverable. (PCI Requirement 3.2)

Payment systems must not store of sensitive authentication data in any form after authorization (even if encrypted). Sensitive authentication data is defined as the following:

  • The card verification code or value (three-digit or four-digit number printed on the front or back of a payment card) is not stored under any circumstance. (PCI Requirement 3.2.2)
  • The personal identification number (PIN) for debit card transactions is not to be stored under any circumstance. (PCI Requirement 3.2.3)

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

Transmission of Cardholder Data

In order to safeguard sensitive cardholder data during transmission over open, public networks, GRANITE GOLD SERVICES will use strong cryptography and security protocols (for example, SSL/TLS, IPSEC, SSH, etc.). These controls will be implemented as follows: (PCI Requirement 4.1)

  • Only trusted keys and certificates are accepted.
  • The protocol in use only supports secure versions or configurations.
  • The encryption strength is appropriate for the encryption methodology in use.

Requirement 5: use and Regularly Update Anti-Virus Software or Programs

Anti-Virus Protection

All systems, particularly personal computers and servers commonly affected by viruses, must have installed an anti-virus program which is capable of detecting, removing, and protecting against all know types of malicious software. (PCI Requirement 5.1, 5.1.1)

For systems considered to be not commonly affected by malicious software, GRANITE GOLD SERVICES will perform periodic evaluations to identify and evaluate evolving malware threats in order to confirm whether such systems continue to not require anti-virus software. (PCI Requirement 5.1.2)

All anti-virus programs must be kept current through automatic updates, be actively running, be configured to run periodic scans, and be capable of as well as configured to generate audit logs. Anti-virus logs must also be retained in accordance with PCI requirement 10.7. (PCI Requirement 5.2)

Steps must be taken to insure that anti-virus mechanisms are actively running and cannot be disabled or altered by users, unless specifically authorized by management on a case-by-case basis for a limited time period. (PCI Requirement 5.3)

Requirement 6:  Develop and Maintain Secure Systems and Applications

Risk and Vulnerability

GRANITE GOLD SERVICES will establish a process to identify security vulnerabilities, using reputable outside sources for security vulnerability information, and assign a risk ranking (for example, as “high,” “medium,” or “low”) to newly discovered security vulnerabilities.

Risk rankings are to be based on industry best practices as well as consideration of potential impact. For example, criteria for ranking vulnerabilities may include consideration of the CVSS base score, and/or the classification by the vendor, and/or type of systems affected. Methods for evaluating vulnerabilities and assigning risk ratings will vary based on an organization’s environment and risk-assessment strategy. Risk rankings should, at a minimum, identify all vulnerabilities considered to be a “high risk” to the environment. In addition to the risk ranking, vulnerabilities may be considered “critical” if they pose an imminent threat to the environment, impact critical systems, and/or would result in a potential compromise if not addressed. Examples of critical systems may include security systems, public-facing devices and systems, databases, and other systems that store, process, or transmit cardholder data. (PCI Requirement 6.1)

All critical security patches must be installed with one month of release. This includes relevant patches for operating systems and all installed applications. All applicable non-critical vendor-supplied security patches are installed within an appropriate time frame (for example, within three months). (PCI Requirement 6.2)

Change Control

GRANITE GOLD SERVICES will enforce change control procedures for the implementation of security patches and software modifications to the in-scope system or systems. These procedures must include documented evidence of the following elements for each software change: (PCI Requirement 6.4.5)

  • Documentation of impact. (PCI Requirement
  • Documented change approval by authorized parties. (PCI Requirement
  • Functionality testing to verify that the change does not adversely impact the security of the system. (PCI Requirement
  • Back-out procedures. (PCI Requirement

Software Development

GRANITE GOLD SERVICES’s software development practice will incorporate secure coding techniques at all levels of the development life cycle. Application developers should be properly trained to identify and resolve issues related to common coding vulnerabilities. Having staff knowledgeable of secure coding guidelines should minimize the number of security vulnerabilities introduced through poor coding practices. Training for developers will be provided in-house or by third parties and should be applicable for technology used to develop the customer facing web code.

All software development will be done with security in mind, and with practices that are aware of the following common issues at a minimum:

  • Injection flaws, particularly SQL injection. Also consider and avoid OS Command Injection, LDAP and XPath injection flaws as well as other injection flaws. Issues of this type can be mitigated by validating input to verify user data cannot modify meaning of commands and queries. Utilizing parameterized queries can also reduce vulnerability to this kind of attack. (PCI Requirement 6.5.1)
  • Buffer overflows, These can be avoided by validating buffer boundaries and/or truncating input strings. (PCI Requirement 6.5.2)
  • Cross-site scripting (XSS) attacks. Validating all parameters before inclusion can help here, as well as utilizing context-sensitive escaping. (PCI Requirement 6.5.7)
  • Improper access control (such as insecure direct object references, failure to restrict URL access, directory traversal, and failure to restrict user access to functions). Proper authentication of users can avoid this type of issue. Sanitizing input and not exposing internal object references to users also help. Coding user interfaces that do not permit access to unauthorized functions is good practice. (PCI Requirement 6.5.8)
  • Cross-site request forgery (CSRF) attacks are addressed by coding techniques that ensure applications do not rely on authorization credentials and tokens automatically submitted by browsers. (PCI Requirement 6.5.9)
  • Broken authentication and session management. Flagging session tokens (for example cookies) as “secure” and not exposing session IDs in the URL will help. Incorporating appropriate time-outs and rotation of session IDs after a successful login will also reduce vulnerability to this. (PCI Requirement 6.5.10)

The vulnerabilities listed above were current with industry best practices when version 3.0 of the PCI DSS was published. However, as industry best practices for vulnerability management are updated (for example, the OWASP Guide, SANS CWE Top 25, CERT Secure Coding, etc.), the current best practices must be incorporated into the development process.

For the public-facing web applications that are part of the payment process, in addition to secure coding GRANITE GOLD SERVICES must address new threats and vulnerabilities on an ongoing basis. These applications shall be protected against known attacks by one of either of the following methods: (PCI Requirement 6.6)

  • Having reviews of public-facing web applications performed via manual or automated application vulnerability security assessment tools or methods. These reviews would need to be done at least annually and after any changes to the code.
  • Having an automated technical solution installed that detects and prevents web-based attacks (for example, a web-application firewall) in front of public-facing web applications, to continually check all traffic.

Requirement 7:  Restrict Access to Cardholder Data by Business Need to Know

Limit Access to Cardholder Data

Access to GRANITE GOLD SERVICES’s cardholder system components and data is limited to only those individuals whose jobs require such access. (PCI Requirement 7.1)

Access limitations must include the following:

Access rights for privileged user IDs must be restricted to the least privileges necessary to perform job responsibilities. (PCI Requirement 7.1.2)

Privileges must be assigned to individuals based on job classification and function (also called “role-based access control). (PCI Requirement 7.1.3)

Requirement 8:  Assign a Unique ID to Each Person with Computer Access

User Accounts

The following must be followed for all user accounts that have access to the system or systems that are part of the payment environment:

  • Assign all users a unique ID before allowing them to access system components or cardholder data. (PCI Requirement 8.1.1)
  • Immediately revoke access for any terminated users. (PCI Requirement 8.1.3)
  • All accounts used by vendors for remote maintenance shall be enabled only during the time period needed. Vendor remote access accounts must be monitored when in use. (PCI Requirement 8.1.5)
  • Limit repeated access attempts by locking out the user ID after not more than six attempts. (PCI Requirement 8.1.6)
  • Set the lockout duration to a minimum of 30 minutes or until an administrator enables the user ID. (PCI Requirement 8.1.7)

Do not use group, shared, or generic IDs, passwords, or other authentication methods as follows: (PCI Requirement 8.5)

  • Generic user IDs are disabled or removed.
  • Shared user IDs do not exist for system administration and other critical functions.
  • Shared and generic user IDs are not used to administer any system components.


User Authentication

In addition to assigning a unique ID for each user, ensure proper user-authentication management for non-consumer users (i.e.: employees and contractors) and administrators on all system components by employing at least one of the following methods to authenticate all users: (PCI Requirement 8.2)

  • Something you know, such as a password or passphrase
  • Something you have, such as a token device or smart card
  • Something you are, such as a biometric.

Using strong cryptography, render all authentication credentials (such as passwords/phrases) unreadable during transmission and storage on all system components. (PCI Requirement 8.2.1)

Passwords/phrases must meet the following: (PCI Requirement 8.2.3)

  • Require a minimum length of at least seven characters.
  • Contain both numeric and alphabetic characters.

Alternatively, the passwords/phrases must have complexity and strength at least equivalent to the parameters specified above.

Change user passwords/passphrases at least every 90 days. (PCI Requirement 8.2.4)

Do not allow an individual to submit a new password/phrase that is the same as any of the last four passwords/phrases he or she has used. (PCI Requirement 8.2.5)

Set passwords/phrases for first-time use and upon reset to a unique value for each user, and change immediately after the first use. (PCI Requirement 8.2.6)

Where other authentication mechanisms are used (for example, physical or logical security tokens, smart cards, certificates, etc.), use of these mechanisms must be assigned as follows: (PCI Requirement 8.6)

  • Authentication mechanisms must be assigned to an individual account and not shared among multiple accounts.
  • Physical and/or logical controls must be in place to ensure only the intended account can use that mechanism to gain access.

Remote Access

Two-factor authentication must be incorporated for remote access (network-level access originating from outside the network) to the network by employees, administrators, and third parties. (PCI Requirement 8.3)

Requirement 9:  Restrict Physical Access to Cardholder Data

Physically Secure All Areas and Media Containing Cardholder Data

Appropriate facility entry controls must be used to limit and monitor physical access to systems in the cardholder data environment. (PCI requirement 9.1)

Hard copy materials containing confidential or sensitive information (e.g., paper receipts, paper reports, faxes, etc.) are subject to the following storage guidelines:

All media must be physically secured. (PCI requirement 9.5)

Strict control must be maintained over the internal or external distribution of any kind of media containing cardholder data.  These controls shall include: (PCI Requirement 9.6)

  • Media must be classified so the sensitivity of the data can be determined. (PCI Requirement 9.6.1)
  • Media must be sent by a secure carrier or other delivery method that can be accurately tracked. (PCI Requirement 9.6.2)
  • Management approval must be obtained prior to moving the media from the secured area. (PCI Requirement 9.6.3)

Strict control must be maintained over the storage and accessibility of media containing cardholder data. (PCI Requirement 9.7)

Destruction of Data

All media containing cardholder data must be destroyed when no longer needed for business or legal reasons. (PCI requirement 9.8)

Hardcopy media must be destroyed by shredding, incineration or pulping so that cardholder data cannot be reconstructed. (PCI requirement 9.8.1.a)

Containers storing information waiting to be destroyed must be secured (locked) to prevent access to the contents by unauthorized personnel. (PCI requirement 9.8.1.b)

Requirement 10:  Regularly Monitor and Test Networks

Audit Log Collection

GRANITE GOLD SERVICES will implement technical controls that create audit trails in order to link all access to system components to an individual user. The automated audit trails created will capture sufficient detail to reconstruct the following events:

  • All actions taken by any individual with root or administrative privileges. (PCI Requirement 10.2.2)
  • All invalid logical access attempts (failed logins). (PCI Requirement 10.2.4)
  • Any use of and changes to identification and authentication mechanisms—including but not limited to creation of new accounts and elevation of privileges—and all changes, additions, or deletions to accounts with root or administrative privileges. (PCI Requirement 10.2.5)

GRANITE GOLD SERVICES’s log generating and collecting solution will capture the following data elements for the above events:

  • User identification. (PCI Requirement 10.3.1)
  • Type of event. (PCI Requirement 10.3.2)
  • Date and time. (PCI Requirement 10.3.3)
  • Success or failure indication. (PCI Requirement 10.3.4)
  • Origination of event. (PCI Requirement 10.3.5)
  • Identity or name of affected data, system component, or resource. (PCI Requirement 10.3.6)

Write logs for external-facing technologies such as the web server that provides the payment service onto a secure, centralized, internal log server or media device. (PCI Requirement 10.5.4)

Audit Log Review

GRANITE GOLD SERVICES’s systems administrators will perform daily review of the audit logs. This review may be manual or automated but must monitor for and evaluate: (PCI Requirement 10.6.1)

  • All security events.
  • Logs of all system components that store, process, or transmit CHD and/or SAD, or that could impact the security of CHD and/or SAD.
  • Logs of all critical system components.
  • Logs of all servers and system components that perform security functions (for example, firewalls, intrusion-detection systems/intrusion-prevention systems (IDS/IPS), authentication servers, e-commerce redirection servers, etc.).

The audit review must also check the logs of all other system components periodically based on the organization’s policies and risk management strategy, as determined by the organization’s annual risk assessment. (PCI Requirement 10.6.2)

Subsequent to log review, systems administrators or other responsible personnel will follow up exceptions and anomalies identified during the review process. (PCI Requirement 10.6.3)

GRANITE GOLD SERVICES must retain audit trail history for at least one year, with a minimum of three months immediately available for analysis (for example, online, archived, or restorable from backup). (PCI Requirement 10.7)


Requirement 11:  Regularly Test Security Systems and Processes


Vulnerability Scanning

At least quarterly, and after any significant changes in the network (such as new system component installations, changes in network topology, firewall rule modifications, product upgrades), GRANITE GOLD SERVICES will perform vulnerability scanning on all in-scope systems.  (PCI Requirement 11.2)

Quarterly external vulnerability scan results must satisfy the ASV Program guide requirements (for example, no vulnerabilities rated higher than a 4.0 by the CVSS and no automatic failures).  External vulnerability scans must be performed by an Approved Scanning Vendor (ASV), approved by the Payment Card Industry Security Standards Council (PCI SSC). Scan reports must be retained for a minimum of a year. (PCI Requirement 11.2.2)

For external vulnerability scans, GRANITE GOLD SERVICES shall perform rescans as needed to validate remediation of failures detected during previous scans, as well as after any significant change to the network. Scans must be performed and reviewed by qualified personnel. (PCI Requirement 11.2.3)

Penetration Testing

Penetration testing of the system or systems providing the payment service must be performed by a qualified individual who implements a methodology for penetration testing that includes the following: (PCI Requirement 11.3)

  • Is based on industry-accepted penetration testing approaches (for example, NIST SP800-115).
  • Includes coverage for the entire CDE perimeter and critical systems.
  • Includes testing from both inside and outside the network.
  • Includes testing to validate any segmentation and scope-reduction controls.
  • Defines application-layer penetration tests to include, at a minimum, the vulnerabilities listed in Requirement 6.5.
  • Defines network-layer penetration tests to include components that support network functions as well as operating systems.
  • Includes review and consideration of threats and vulnerabilities experienced in the last 12 months.
  • Specifies retention of penetration testing results and remediation activities results.

Perform external penetration testing at least annually and after any significant infrastructure or application upgrade or modification (such as an operating system upgrade, a sub-network added to the environment, or a web server added to the environment). (PCI Requirement 11.3.1)

When exploitable vulnerabilities are found during penetration testing, the vulnerabilities must be corrected and testing then repeated to verify the corrections were effective. (PCI Requirement 11.3.3)

If segmentation is used to isolate the CDE from other networks, perform tests at least annually and after any changes to segmentation controls/methods to verify that the segmentation methods are operational and effective, and isolate all out-of-scope systems from in-scope systems. These tests need to be done from multiple locations on the internal network, checking both for improper accessibility from the out-of-scope zones to the in-scope zone as well as the reverse. (PCI Requirement 11.3.4)

Change Detection

For all in-scope systems for which it is technically possible, GRANITE GOLD SERVICES must deploy a change-detection mechanism (for example, file-integrity monitoring tools) to alert personnel to unauthorized modification of critical system files, configuration files, or content files; and configure the software to perform critical file comparisons at least weekly. The change detection software must be integrated with the logging solution described above, and it must be capable of raising alerts to responsible personnel. (PCI Requirement 11.5.1)

For change-detection purposes, critical files are usually those that do not regularly change, but the modification of which could indicate a system compromise or risk of compromise. Change-detection mechanisms such as file-integrity monitoring products usually come pre-configured with critical files for the related operating system. Other critical files, such as those for custom applications, must be evaluated and defined by the entity (that is, the merchant or service provider). (PCI Requirement 11.5)

Requirement 12:  Maintain a Policy that Addresses Information Security for Employees and Contractors

Security Policy       

GRANITE GOLD SERVICES shall establish, publish, maintain, and disseminate a security policy that addresses how the company will protect cardholder data. (PCI Requirement 12.1)

This policy must be reviewed at least annually, and must be updated as needed to reflect changes to business objectives or the risk environment.  (PCI requirement 12.1.1)

Security Responsibilities

GRANITE GOLD SERVICES’s policies and procedures must clearly define information security responsibilities for all personnel. (PCI Requirement 12.4)

Incident Response Policy

The Security Manager shall establish, document, and distribute security incident response and escalation procedures to ensure timely and effective handling of all situations.  (PCI requirement 12.5.3)

Incident Identification

Employees must be aware of their responsibilities in detecting security incidents to facilitate the incident response plan and procedures.  All employees have the responsibility to assist in the incident response procedures within their particular areas of responsibility.  Some examples of security incidents that an employee might recognize in their day to day activities include, but are not limited to,

  • Theft, damage, or unauthorized access (e.g., papers missing from their desk, broken locks, missing log files, alert from a security guard, video evidence of a break-in or unscheduled/unauthorized physical entry).
  • Fraud – Inaccurate information within databases, logs, files or paper records.

Reporting an Incident

The Security Manager should be notified immediately of any suspected or real security incidents involving cardholder data:

Contact the Security Manager to report any suspected or actual incidents. The Internal Audit’s phone number should be well known to all employees and should page someone during non-business hours.

No one should communicate with anyone outside of their supervisor(s) or the Security Manager about any details or generalities surrounding any suspected or actual incident.  All communications with law enforcement or the public will be coordinated by the Security Manager.

Document any information you know while waiting for the Security Manager to respond to the incident. If known, this must include date, time, and the nature of the incident. Any information you can provide will aid in responding in an appropriate manner.


Incident Response Policy (PCI requirement 12.10.1)

Responses can include or proceed through the following stages: identification, severity classification, containment, eradication, recovery and root cause analysis resulting in improvement of security controls.

Contain, Eradicate, Recover and perform Root Cause Analysis

  1. Notify applicable card associations.


Provide the compromised Visa accounts to Visa Fraud Control Group within ten (10) business days. For assistance, contact 1-(650)-432-2978. Account numbers must be securely sent to Visa as instructed by the Visa Fraud Control Group. It is critical that all potentially compromised accounts are provided. Visa will distribute the compromised Visa account numbers to issuers and ensure the confidentiality of entity and non-public information.  See Visa’s “What to do if compromised” documentation for additional activities that must be performed.  That documentation can be found at


Contact your merchant bank for specific details on what to do following a compromise.  Details on the merchant bank (aka. the acquirer) can be found in the Merchant Manual at  Your merchant bank will assist when you call MasterCard at 1-(636)-722-4100.

Discover Card

Contact your relationship manager or call the support line at 1-(800)-347-3083 for further guidance.

  1. Alert all necessary parties. Be sure to notify:
  2. Merchant bank
  3. Local FBI Office
  4. S. Secret Service (if Visa payment data is compromised)
  5. Local authorities (if appropriate)
  6. Perform an analysis of legal requirements for reporting compromises in every state where clients were affected. The following source of information must be used:
  7. Collect and protect information associated with the intrusion. In the event that forensic investigation is required the Security Manager will work with legal and management to identify appropriate forensic specialists.
  8. Eliminate the intruder’s means of access and any related vulnerabilities.
  9. Research potential risks related to or damage caused by intrusion method used.

Root Cause Analysis and Lessons Learned

Not more than one week following the incident, members of the Security Manager and all affected parties will meet to review the results of any investigation to determine the root cause of the compromise and evaluate the effectiveness of the Incident Response Plan. Review other security controls to determine their appropriateness for the current risks. Any identified areas in which the plan, policy or security control can be made more effective or efficient, must be updated accordingly.

Security Awareness

GRANITE GOLD SERVICES shall establish and maintain a formal security awareness program to make all personnel aware of the importance of cardholder data security. (PCI Requirement 12.6)

Service Providers

GRANITE GOLD SERVICES shall implement and maintain policies and procedures to manage service providers. (PCI requirement 12.8)

This process must include the following:

  • Maintain a list of service providers. (PCI requirement 12.8.1)
  • Maintain a written agreement that includes an acknowledgement that the service providers are responsible for the security of the cardholder data the service providers possess. (PCI requirement 12.8.2)
  • Implement a process to perform proper due diligence prior to engaging a service provider. (PCI requirement 12.8.3)
  • Monitor service providers’ PCI DSS compliance status. (PCI requirement 12.8.4)
  • Maintain information about which PCI DSS requirements are managed by each service provider, and which are managed by the entity. (PCI requirement 12.8.5)

FREE SHIPPING On Orders $50 Or More. Contiguous U.S. States Only.