Table of Contents

Control Environment Narrative

ACME Evil Anvil Corporation

March 2019

Contents

  1. Control Environment Narrative
  2. Logical Controls
  3. Policy Controls
  4. Procedural Controls
    1. Scheduled Security and Audit Procedures
    2. Event-Driven Security and Audit Procedures
  5. Remediations
  6. Communications
    1. Internal
    2. External

Table 1: Control satisfaction

Standard Controls Satisfied
TSC CC2.1, CC2.2, CC2.3, CC4.1, CC4.2, CC5.1, CC5.2, CC5.3

Table 2: Document history

Date Comment
Jun 1 2018 Initial document

Control Environment Narrative

The following provides a description of the control structure of ACME Evil Anvil Corporation. The intent of this description is to enumerate the logical, policy, and procedural controls that serve to monitor ACME Evil Anvil Corporation’s application and data security. Changes uncovered by these procedures in the logical, policy, procedural, or customer environment are addressed by remediations specific to the noted change.

Logical Controls

ACME Evil Anvil Corporation employs several logical controls to protect confidential data and ensure normal operation of its core product.

Policy Controls

ACME Evil Anvil Corporation employs several policy controls to protect confidential data and ensure normal operation of its core product. These policies include, but are not limited to:

Procedural Controls

ACME Evil Anvil Corporation has numerous scheduled procedures to monitor and tune the effectiveness of ongoing security controls, and a series of event-driven procedures to respond to security-related events.

TODO: Finalize these lists

  1. Scheduled Security and Audit Procedures
    1. Review Access [quarterly]
    2. Review Security Logs [weekly]
    3. Review Cyber Risk Assessment (enumerate possible compromise scenarios) [quarterly]
    4. Review Data Classification [quarterly]
    5. Backup Testing [quarterly]
    6. Disaster Recovery Testing [semi-annual]
    7. Review Devices & Workstations [quarterly]
    8. Review & Clear Low-Priority Alerts [weekly]
    9. Apply OS Patches [monthly]
    10. Verify Data Disposal per Retention Policy [quarterly]
    11. Conduct Security Training [annual]
    12. Review Security Monitoring and Alerting Configuration [quarterly]
    13. Penetration Test [annual]
    14. Whitebox Security Review [annual]
    15. SOC2 Audit [annual]
  2. Event-Driven Security and Audit Procedures
    1. Onboard Employee
    2. Offboard Employee
    3. Investigate Security Alert
    4. Investigate Security Incident

Remediations

ACME Evil Anvil Corporation uses the outcomes of the aforementioned controls and procedures to identify shortcomings in the existing control environment. Once identified, these shortcomes are remediated by improving existing controls and procedures, and creating new controls and procedures as needed.

Communications

ACME Evil Anvil Corporation communicates relevant information regarding the functioning of the above controls with internal and external parties on an as-needed basis and according to statutory requirements.

Internal

ACME Evil Anvil Corporation communicates control outcomes, anomalies, and remediations internally using the following channels:

  1. Slack
  2. Email
  3. Github ticketing

External

ACME Evil Anvil Corporation communicates relevant control-related information to external parties including shareholders, customers, contractors, regulators, and government entities as needed according to contractual and regulatory/statutory obligation.