Welcome to Philadelphia Real Estate Classes
Pennsylvania's Premier Real Estate Education Provider
This Policy document encompasses all aspects of security surrounding confidential company information and must be distributed to all company employees. All company employees must read this document in its entirety and sign the form confirming they have read and fully understand this policy. This document will be reviewed and updated by Management on an annual basis or when relevant to include newly developed security standards into the policy and re-distributed to all employees and contractors where applicable.
PRC handles sensitive cardholder information daily. Sensitive Information must have adequate safeguards in place to protect the cardholder data, cardholder privacy, and to ensure compliance with various regulations, along with guarding the future of the organisation.
PRC commits to respecting the privacy of all its customers and to protecting any customer data from outside parties. To this end management are committed to maintaining a secure environment in which to process cardholder information so that we can meet these promises.
Employees handling sensitive cardholder data should ensure:
• Handle Company and cardholder information in a manner that fits with their sensitivity and classification;
• Limit personal use of PRC information and telecommunication systems and ensure it doesn’t interfere with your job performance;
• PRC reserves the right to monitor, access, review, audit, copy, store, or delete any electronic communications, equipment, systems and network traffic for any purpose;
• Do not use e-mail, internet and other Company resources to engage in any action that is offensive, threatening, discriminatory, defamatory, slanderous, pornographic, obscene, harassing or illegal;
• Do not disclose personnel information unless authorized;
• Protect sensitive cardholder information;
• Keep passwords and accounts secure;
• Request approval from management prior to establishing any new software or hardware, third party connections, etc.;
• Do not install unauthorised software or hardware, including modems and wireless access unless you have explicit management approval;
• Always leave desks clear of sensitive cardholder data and lock computer screens when unattended;
• Information security incidents must be reported, without delay, to the individual responsible for incident response locally – Please find out who this is.
We each have a responsibility for ensuring our company’s systems and data are protected from unauthorized access and improper use. If you are unclear about any of the policies detailed herein you should seek advice and guidance from your line manager.
A high-level network diagram of the network is maintained and reviewed on a yearly basis. The network diagram provides a high level overview of the cardholder data environment (CDE), which at a minimum shows the connections in and out of the CDE. Critical system components within the CDE, such as POS devices, databases, web servers, etc., and any other necessary payment components, as applicable should also be illustrated.
In addition, ASV should be performed and completed by a PCI SSC Approved Scanning Vendor, where applicable. Evidence of these scans should be maintained for a period of 18 months.
Management’s intentions for publishing an Acceptable Use Policy are not to impose restrictions that are contrary to PRC’s established culture of openness, trust and integrity. Management is committed to protecting the employees, partners and the Company from illegal or damaging actions, either knowingly or unknowingly by individuals. PRC will maintain an approved list of technologies and devices and personnel with access to such devices as detailed in Appendix B.
It is strictly prohibited to store:
Data and media containing data must always be labelled to indicate sensitivity level.
All Access to sensitive cardholder should be controlled and authorised. Any job functions that require access to cardholder data should be clearly defined.
Access to sensitive information in both hard and soft media format must be physically restricted to prevent unauthorised individuals from obtaining sensitive data.
All sensitive cardholder data must be protected securely if it is to be transported physically or electronically.
• All data must be securely disposed of when no longer required by PRC, regardless of the media or application type on which it is stored.
• An automatic process must exist to permanently delete on-line data, when no longer required.
• All hard copies of cardholder data must be manually destroyed when no longer required for valid and justified business reasons. A quarterly process must be in place to confirm that all non-electronic cardholder data has been appropriately disposed of in a timely manner.
• PRC will have procedures for the destruction of hardcopy (paper) materials. These will require that all hardcopy materials are crosscut shredded, incinerated or pulped so they cannot be reconstructed.
• PRC will have documented procedures for the destruction of electronic media. These will require:
• All cardholder data on electronic media must be rendered unrecoverable when deleted e.g. through degaussing or electronically wiped using military grade secure deletion processes or the physical destruction of the media;
• If secure wipe programs are used, the process must define the industry accepted standards followed for secure deletion.
• All cardholder information awaiting destruction must be held in lockable storage containers clearly marked “To Be Shredded” - access to these containers must be restricted.
The policies and procedures outlined below must be incorporated into company practice to maintain a high level of security awareness. The protection of sensitive data demands regular training of all employees and contractors.
• Review handling procedures for sensitive information and hold periodic security awareness meetings to incorporate these procedures into day to day company practice.
• Distribute this security policy document to all company employees to read. It is required that all employees confirm that they understand the content of this security policy document by signing an acknowledgement form (see Appendix A).
• All employees that handle sensitive information will undergo background checks (such as criminal and credit record checks, within the limits of the local law) before they commence their employment with PRC.
• All third parties with access to credit card account numbers are contractually obligated to comply with card association security standards (PCI/DSS).
• Company security policies must be reviewed annually and updated as needed.
• PRC PCI Security Incident Response Team (PCI Response Team) is comprised of the Information Security Officer and Merchant Services. PRC PCI security incident response plan is as follows:
• Each department must report an incident to the Information Security Officer (preferably) or to another member of the PCI Response Team.
• That member of the team receiving the report will advise the PCI Response Team of the incident.
• The PCI Response Team will investigate the incident and assist the potentially compromised department in limiting the exposure of cardholder data and in mitigating the risks associated with the incident.
• The PCI Response Team will resolve the problem to the satisfaction of all parties involved, including reporting the incident and findings to the appropriate parties (credit card associations, credit card processors, etc.) as necessary.
• The PCI Response Team will determine if policies and processes need to be updated to avoid a similar incident in the future, and whether additional safeguards are required in the environment where the incident occurred, or for the institution.
PRC PCI Security Incident Response Team (or equivalent in your organization):
CIO | Mark Cumberland |
---|---|
Communications Director | Mark Cumberland |
Compliance Officer | Mark Cumberland |
Counsel | n/a |
Information Security Officer | Mark Cumberland |
Collections & Merchant Services | Kathleen Galante |
Risk Manager | Mark Cumberland |
A department that reasonably believes it may have an account breach, or a breach of cardholder information or of systems related to the PCI environment in general, must inform PRC PCI Incident Response Team. After being notified of a compromise, the PCI Response Team, along with other designated staff, will implement the PCI Incident Response Plan to assist and augment departments’ response plans.
Escalation Members (or equivalent in your company):
Escalation – First Level:
Information Security Officer Controller
Executive Project Director for Credit Collections and Merchant Services Legal Counsel
Risk Manager
Director of PRC Communications
Escalation – Second Level:
PRC President
Executive Cabinet
Internal Audit
Auxiliary members as needed
External Contacts (as needed):
Merchant Provider Card Brands
Internet Service Provider (if applicable)
Internet Service Provider of Intruder (if applicable) Communication Carriers (local and long distance) Business Partners
Insurance Carrier
External Response Team as applicable (CERT Coordination Center 1, etc) Law Enforcement Agencies as applicable inn local jurisdiction
In response to a systems compromise, the PCI Response Team and designees will:
• Ensure compromised system/s is isolated on/from the network.
• Gather, review and analyze the logs and related information from various central and local safeguards and security controls
• Conduct appropriate forensic analysis of compromised system.
• Contact internal and external departments and entities as appropriate.
• Make forensic and log analysis available to appropriate law enforcement or card industry security personnel, as required.
• Assist law enforcement and card industry security personnel in investigative processes, including in prosecutions.
The credit card companies have individually specific requirements that the Response Team must address in reporting suspected or confirmed breaches of cardholder data. See below for these requirements.
Incident Response notifications to various card schemes
• In the event of a suspected security breach, alert the information security officer or your line manager immediately.
• The security officer will carry out an initial investigation of the suspected security breach.
• Upon confirmation that a security breach has occurred, the security officer will alert management and begin informing all relevant parties that may be affected by the compromise.
VISA Steps
If the data security compromise involves credit card account numbers, implement the following procedure:
• Shut down any systems or processes involved in the breach to limit the extent, and prevent further exposure.
• Alert all affected parties and authorities such as the Merchant Bank (your Bank), Visa Fraud Control, and the law enforcement.
• Provide details of all compromised or potentially compromised card numbers to Visa Fraud Control within 24 hrs.
• For more Information visit: http://usa.visa.com/business/accepting_visa/ops_risk_management/cisp_if_ compromised.html
Visa Incident Report Template
This report must be provided to VISA within 14 days after initial report of incident to VISA. The following report content and standards must be followed when completing the incident report. Incident report must be securely distributed to VISA and Merchant Bank. Visa will classify the report as “VISA Secret”*.
• Executive Summary
• Include overview of the incident
• Include RISK Level(High, Medium, Low)
• Determine if compromise has been contained
• Background
• Initial Analysis
• Investigative Procedures
• Include forensic tools used during investigation
• Findings
• Number of accounts at risk, identify those stores and compromised
• Type of account information at risk
• Identify ALL systems analyzed. Include the following:
• Domain Name System (DNS) names
• Internet Protocol (IP) addresses
• Operating System (OS) version
• Function of system(s)
• Identify ALL compromised systems. Include the following:
• DNS names
• IP addresses
• OS version
• Function of System(s)
• Timeframe of compromise
• Any data exported by intruder
• Establish how and source of compromise
• Check all potential database locations to ensure that no CVV2, Track 1 or Track 2 data is stored anywhere, whether encrypted or unencrypted (e.g., duplicate or backup tables or databases, databases used in development, stage or testing environments, data on software engineers’ machines, etc.)
• If applicable, review VisaNet endpoint security and determine risk
• Compromised Entity Action
• Recommendations
• Contact(s) at entity and security assessor performing investigation
*This classification applies to the most sensitive business information, which is intended for use within VISA. Its unauthorized disclosure could seriously and adversely impact VISA, its employees, member banks, business partners, and/or the Brand.
MasterCard Steps:
• Within 24 hours of an account compromise event, notify the MasterCard Compromised Account Team via phone at 1-636-722-4100.
• Provide a detailed written statement of fact about the account compromise (including the contributing circumstances) via secured e-mail to compromised_account_team@mastercard.com.
• Provide the MasterCard Merchant Fraud Control Department with a complete list of all known compromised account numbers.
• Within 72 hours of knowledge of a suspected account compromise, engage the services of a data security firm acceptable to MasterCard to assess the vulnerability of the compromised data and related systems (such as a detailed forensics evaluation).
• Provide weekly written status reports to MasterCard, addressing open questions and issues until the audit is complete to the satisfaction of MasterCard.
• Promptly furnish updated lists of potential or known compromised account numbers, additional documentation, and other information that MasterCard may request.
• Provide finding of all audits and investigations to the MasterCard Merchant Fraud Control department within the required time frame and continue to address any outstanding exposure or recommendation until resolved to the satisfaction of MasterCard.
Once MasterCard obtains the details of the account data compromise and the list of compromised account numbers, MasterCard will:
• Identify the issuers of the accounts that were suspected to have been compromised and group all known accounts under the respective parent member IDs.
• Distribute the account number data to its respective issuers.
Employees of the company will be expected to report to the security officer for any security related issues. The role of the security officer is to effectively communicate all security policies and procedures to employees within the company and contractors. In addition to this, the security officer will oversee the scheduling of security training sessions, monitor and enforce the security policies outlined in both this document and at the training sessions and finally, oversee the implantation of the incident response plan in the event of a sensitive data compromise.
Discover Card Steps
• Within 24 hours of an account compromise event, notify Discover Fraud Prevention at (800) 347-3102
• Prepare a detailed written statement of fact about the account compromise including the contributing circumstances
• Prepare a list of all known compromised account numbers
• Obtain additional specific requirements from Discover Card
American Express Steps
• Within 24 hours of an account compromise event, notify American Express Merchant Services at (800) 528-5200 in the U.S.
• Prepare a detailed written statement of fact about the account compromise including the contributing circumstances
• Prepare a list of all known compromised account numbers Obtain additional specific requirements from American Express
Transfer of Sensitive Information Policy
• All third-party companies providing critical services to PRC must provide an agreed Service Level Agreement.
• All third-party companies providing hosting facilities must comply with the Company’s Physical Security and Access Control Policy.
• All third-party companies which have access to Card Holder information must
• Adhere to the PCI DSS security requirements.
• Acknowledge their responsibility for securing the Card Holder data.
• Acknowledge that the Card Holder data must only be used for assisting the completion of a transaction, supporting a loyalty program, providing a fraud control service or for uses specifically required by law.
• Have appropriate provisions for business continuity in the event of a major disruption, disaster or failure.
• Provide full cooperation and access to conduct a thorough security review after a security intrusion by a Payment Card industry representative, or a Payment Card industry approved third party.
User Access Management
• Access to Company is controlled through a formal user registration process beginning with a formal notification from HR or from a line manager.
• Each user is identified by a unique user ID so that users can be linked to and made responsible for their actions. The use of group IDs is only permitted where they are suitable for the work carried out.
• There is a standard level of access; other services can be accessed when specifically authorized by HR/line management.
• The job function of the user decides the level of access the employee has to cardholder data
• A request for service must be made in writing (email or hard copy) by the newcomer’s line manager or by HR. The request is free format, but must state:
Name of person making request;
Job title of the newcomers and workgroup;
Start date;
Services required (default services are: MS Outlook, MS Office and Internet access).
• Each user will be given a copy of their new user form to provide a written statement of their access rights, signed by an IT representative after their induction procedure. The user signs the form indicating that they understand the conditions of access.
• Access to all PRC systems is provided by IT and can only be started after proper procedures are completed.
• As soon as an individual leaves PRC employment, all his/her system logons must be immediately revoked.
• As part of the employee termination process HR (or line managers in the case of contractors) will inform IT operations of all leavers and their date of leaving.
• Access Control systems are in place to protect the interests of all users of PRC computer systems by providing a safe, secure and readily accessible environment in which to work.
• PRC will provide all employees and other users with the information they need to carry out their responsibilities in an as effective and efficient manner as possible.
• Generic or group IDs shall not normally be permitted, but may be granted under exceptional circumstances if sufficient other controls on access are in place.
• The allocation of privilege rights (e.g. local administrator, domain administrator, super-user, root access) shall be restricted and controlled, and authorization provided jointly by the system owner and IT Services. Technical teams shall guard against issuing privilege rights to entire teams to prevent loss of confidentiality.
• Access rights will be accorded following the principles of least privilege and need to know.
• Every user should attempt to maintain the security of data at its classified level even if technical security mechanisms fail or are absent.
• Users electing to place information on digital media or storage devices or maintaining a separate database must only do so where such an action is in accord with the data’s classification.
• Users are obligated to report instances of non-compliance to PRC CISO.
• Access to PRC IT resources and services will be given through the provision of a unique Active Directory account and complex password.
• No access to any PRC IT resources and services will be provided without prior authentication and authorization of a user’s PRC Windows Active Directory account.
• Password issuing, strength requirements, changing and control will be managed through formal processes. Password length, complexity and expiration times will be controlled through Windows Active Directory Group Policy Objects.
• Access to Confidential, Restricted and Protected information will be limited to authorised persons whose job responsibilities require it, as determined by the data owner or their designated representative. Requests for access permission to be granted, changed or revoked must be made in writing.
• Users are expected to become familiar with and abide by PRC policies, standards and guidelines for appropriate and acceptable usage of the networks and systems.
• Access for remote users shall be subject to authorization by IT Services and be provided in accordance with the Remote Access Policy and the Information Security Policy. No uncontrolled external access shall be permitted to any network device or networked system.
• Access to data is variously and appropriately controlled according to the data classification levels described in the Information Security Management Policy.
• Access control methods include logon access rights, Windows share and NTFS permissions, user account privileges, server and workstation access rights, firewall permissions, IIS intranet/extranet authentication rights, SQL database rights, isolated networks and other methods as necessary.
• A formal process shall be conducted at regular intervals by system owners and data owners in conjunction with IT Services to review users’ access rights. The review shall be logged and IT Services shall sign off the review to give authority for users’ continued access rights.
215-335-6919
Mark@PhiladelphiaRealEstateClasses.com
9227 Franford Ave
Philadelphia, PA, 19114