Skip to content

Security Policy Draft (FTC v. Drizly 2022)

Draft or update enterprise security policy to support FTC consent order and program maturity.


Purpose

Policies that support the consent order and address FTC findings: (1) Information security program policy — scope, coordinator, risk assessment, safeguards, training, testing, service provider oversight. (2) Access control and authentication policy — MFA requirements, password standards, role-based access, offboarding. (3) Secure development and credential management — no credentials in source code; repository scanning; change review. (4) Data retention and minimization policy — retention schedule, deletion or de-identification of unnecessary personal information. Policies should be written, approved, and available for examiner review.


Hallucinated writing examples

Scenario. In November 2022, after the FTC accepted the consent order (time), the Security Director (role) submits a security policy draft (type) to the CISO (audience) for approval and rollout to support information security program and retention obligations.

SECURITY POLICY DRAFT — SUMMARY FOR APPROVAL

To: Chief Information Security Officer
From: Security Director
Date: November 22, 2022
Re: Policy Package — Information Security Program, IAM, Secure Development, and Data Retention

This package summarizes the core policies required to operate the information security program and data minimization obligations reflected in the FTC Decision and Order (FTC Docket No. 2023185). The scenario is illustrative; the obligations and topics are grounded in the Order and the FTC’s complaint allegations.

1) Information Security Program Policy (Program Governance).
Defines program scope, designated coordinator, risk assessment cadence, safeguards, training, testing and monitoring, service provider oversight, and documentation and evidence requirements.

2) Access Control and Authentication Policy (IAM).
Requires MFA for accounts with access to source code or production credentials; defines role-based access, access reviews, account lifecycle controls, and password and session standards where applicable.

3) Secure Development and Credential Management Policy (Secrets).
Prohibits secrets in source code or repositories; requires automated secret scanning, credential rotation workflows, change review for high-risk settings, and incident handling for credential exposure.

4) Data Minimization and Retention Policy (Data Security).
Implements a retention schedule; requires deletion or de-identification when data is no longer necessary; limits collection and use to what is necessary for specified purposes; defines evidence and auditability.

Requested approval. Approve the policy package for publication and enforcement, including policy ownership, effective dates, and quarterly compliance reporting.

Primary sources

© 2026 Yi Zhang. Licensed under the MIT License.
Last updated: