ID Dataweb, Inc. Access Security Requirements

The security requirements included here represent the minimum security requirements acceptable to ID Dataweb, Inc., (“IDW”) and are intended to ensure that each IDW customer and supplier (“Third Party”) has appropriate controls in place to protect information and systems, including any information that it receives, processes, transfers, transmits, stores, delivers, and / or otherwise accesses IDW information. 

DEFINITIONS 

“IDW Information” means highly sensitive information including, by way of example and not limitation, data, databases, application software, software documentation, supporting process documents, operation process and procedures documentation, test plans, test cases, test scenarios, cyber incident reports, consumer information, financial records, employee records, and information about potential acquisitions, and such other information that is similar in nature or as mutually agreed in writing, the disclosure, alteration or destruction of which would cause serious damage to IDW’S reputation, valuation, and / or provide a competitive disadvantage to IDW. 

“Resource” means all Third-Party devices, including but not limited to laptops, PCs, routers, servers, and other computer systems that store, process, transfer, transmit, deliver, or otherwise access IDW Information.

1. Information Security Policies and Governance

Third Party shall have Information Security policies and procedures in place that are consistent with the practices described in an industry standard, such as ISO 27002 and / or this Security Requirements document, which is aligned to IDW’s Information Security policy. 

Third Party shall implement and maintain a comprehensive information security program written in one of or more readily accessible parts and that contains administrative, technical, and physical safeguards that are appropriate to the their size and complexity, the nature and scope of its activities, and the sensitivity of the information provided to them by IDW. 

Third Party shall ensure that such safeguards shall include the elements set forth in16 C.F.R. § 314.4 and shall be reasonably designed to: 

• insure the security and confidentiality of the information provided by reseller,
• protect against any anticipated threats or hazards to the security or integrity of such information, and
• protect against unauthorized access to or use of such information that could result in substantial harm or incontinence to any consumer.

2. Vulnerability Management

Firewalls, routers, servers, PCs, and all other resources managed by Third Party (including physical, on-premise or cloud hosted infrastructure) will be kept current with appropriate security specific system patches. Third Party will perform regular penetration tests to further assess the security of systems and resources. Third Party will use end-point computer malware detection / scanning services and procedures.

3. Logging and Monitoring

Logging mechanisms will be in place sufficient to identify security incidents, establish individual accountability, and reconstruct events. Audit logs will be retained in a protected state (i.e., encrypted, or locked) with a process for periodic review.

4. Network Security

Third Party will use security measures, including anti-virus software, to protect communications systems and networks device to reduce the risk of infiltration, hacking, access penetration by, or exposure to, an unauthorized third-party.

5. Data Security

Third Party will use security measures, including encryption, to protect Experian provided data in storage and in transit to reduce the risk of exposure to unauthorized parties.

6. Remote Access Connection Authorization

All remote access connections to Third Party internal networks and / or computer systems will require authorization with access control at the point of entry using multi-factor authentication. Such access will use secure channels, such as a Virtual Private Network (VPN).

7. Incident Response

Processes and procedures will be established for responding to security violations and unusual or suspicious events and incidents. Third Party will report actual or suspected security violations or incidents that may affect IDW to IDW within twenty-four (24) hours of Third Party’s confirmation of such violation or incident.

8. Identification, Authentication and Authorization

Each user of any Resource will have a uniquely assigned user ID to enable individual authentication and accountability. Access to privileged accounts will be restricted to those people who administer the Resource and individual accountability will be maintained. All default passwords (such as those from hardware or software vendors) will be changed immediately upon receipt.

9. User Passwords and Accounts

All passwords will remain confidential and use ‘strong’ passwords that expire after a maximum of 90 calendar days. Accounts will automatically lockout after five (5) consecutive failed login attempts.

10. Training and Awareness

Third Party shall require all Third Party personnel to participate in information security training and awareness sessions at least annually and establish proof of learning for all personnel.

11. Right to Audit

Third Party shall be subject to remote and / or onsite assessments of its information security controls and compliance with these access security requirements.

12. Bulk Email Communications

Third party will not “bulk email” communications to multiple IDW employees without the prior written approval of IDW. Third party shall seek authorization via their IDW account executive in advance of any such campaign. 

Data Protection Officer 

If you need to reach our Data Protection Officer, his contact information is:  

Timothy Snyder  

ID Dataweb, Inc.

8330 Boone Blvd,

Suite 400 

Vienna, VA 22182  

Compliance@iddataweb.com  

571-442-6117