Acquisition Assessment Policy

1. Overview

The process of integrating a newly acquired company can have a drastic impact on the security poster of either the parent company or the child company.  The network and security infrastructure of both entities may vary greatly, and the workforce of the new company may have a drastically different culture and tolerance to openness.  The goal of the security acquisition assessment and integration process should include:

2. Purpose

The purpose of this policy is to establish Infosec responsibilities regarding corporate acquisitions and define the minimum security requirements of an Infosec acquisition assessment.

3. Scope

This policy applies to all companies acquired by eCuras. It pertains to all systems, networks, laboratories, test equipment, hardware, software, and firmware, owned and/or operated by the acquired company.

4. Policy

4.1   General

Acquisition assessments are conducted to ensure that a company being acquired by eCuras does not pose a security risk to corporate networks, internal systems, and/or confidential/sensitive information. The Infosec Team will provide personnel to serve as active members of the acquisition team throughout the entire acquisition process. Infosec role is to detect and evaluate information security risk, develop a remediation plan with the affected parties for the identified risk, and work with the acquisitions team to implement solutions for any identified security risks, before allowing connectivity to eCuras’s networks. Below are the minimum requirements that the acquired company must meet before being connected to the eCuras network.

4.2   Requirements

4.2.1        Hosts  All hosts (servers, desktops, laptops) will be replaced or re-imaged with a eCuras standard image or required to adopt the minimum standards for end-user devices.  Business-critical production servers that cannot be replaced or re-imaged must be audited and a waiver granted by Infosec.  All PC based hosts will require eCuras approved virus protection before the network connection.

4.2.2        Networks  All network devices will be replaced or re-imaged with a eCuras standard image.  Wireless network access points will be configured to the eCuras standard.

4.2.3        Internet  All Internet connections will be terminated.  When justified by business requirements, air-gapped Internet connections require Infosec review and approval.

4.2.4        Remote Access  All remote access connections will be terminated.  Remote access to the production network will be provided by eCuras.

4.2.5        Labs  Lab equipment must be physically separated and secured from non-lab areas.  The lab network must be separated from the corporate production network with a firewall between the two networks.  Any direct network connections (including analog lines, ISDN lines, T1, etc.) to external customers, partners, etc., must be reviewed and approved by the Lab Security Group (LabSec).  All acquired labs must meet with LabSec lab policy or be granted a waiver by Labtec.  In the event the acquired networks and computer systems being connected to the corporate network fail to meet these requirements, the eCuras Chief Information Officer (CIO) must acknowledge and approve of the risk to eCuras’s networks.

5. Policy Compliance

5.1  Compliance Measurement

The Infosec team will verify compliance with this policy through various methods, including but not limited to business tool reports, internal and external audits, and feedback to the policy owner.

5.2  Exceptions

The Infosec team must approve any exception to the policy in advance.

5.3  Non-Compliance

An employee found to have violated this policy may be subject to disciplinary action, up to and including termination of employment. 

Revised: March 14th, 2018

Table of Content

  1. Acceptable Encryption Policy
  2. Acceptable Use Policy
  3. Clean Desc Policy
  4. Data Breach Response Policy
  5. Disaster Recovery Plan Policy
  6. Digital Signature Acceptance Policy
  7. Email Policy
  8. Ethics Policy
  9. Pandemic Response Planning Policy
  10. Password Construction Guidelines
  11. Password Protection Policy
  12. Security Response Plan Policy
  13. End User Encryption Key Protection Policy
  14. Acquisition Assessment Policy
  15. Bluetooth Baseline Requirements Policy
  16. Remote Access Policy
  17. Remote Access Tools Policy
  18. Router and Switch Security Policy
  19. Wireless Communication Policy
  20. Wireless Communication Standard
  21. Database Credentials Policy
  22. Technology Equipment Disposal Policy
  23. Information Logging Standard
  24. Lab Security Policy
  25. Server Security Policy 
  26. Software Installation Policy
  27. Workstation Security (For HIPAA) Policy
  28. Web Application Security Policy
  29.  Analog/ISDN Line Security Policy
  30. Anti-Virus Guidelines
  31. Server Audit Policy
  32. Automatically Forwarded Email Policy
  33. Communications Equipment Policy
  34. Dial In Access Policy
  35. Extranet Policy
  36. Internet DMZ Equipment Policy
  37. Internet Usage Policy
  38. Mobile Device Encryption Policy
  39. Personal Communication Devices and Voicemail Policy
  40. Removable Media Policy
  41. Risk Assessment Policy
  42. Server Malware Protection Policy
  43. Social Engineering Awareness Policy
  44. DMZ Lab Security Policy
  45. Email Retention Policy
  46. Employee Internet Use Monitoring and Filtering Policy
  47. Lab Anti Virus Policy
  48. Mobile Employee Endpoint Responsibility Policy
  49. Remote Access Mobile Computing Storage
  50. Virtual Private Network Policy