NYDFS Cybersecurity Regulation Control Mapping

Overview

This document maps NYDFS Cybersecurity Regulation requirements to specific AWS controls and evidence collection points. It serves as a reference for compliance assessments and audit preparation.

Control Mapping Matrix

Section 500.02: Cybersecurity Program

NYDFS ControlAWS ControlEvidence TypeCollection MethodStatus
500.02(a) - Risk AssessmentAWS Config RulesAutomatedAWS Config✅
500.02(b) - Defense in DepthSecurity Groups, NACLsAutomatedAWS Security Hub✅
500.02(c) - Access ControlsIAM PoliciesAutomatedAWS IAM Access Analyzer✅
500.02(d) - Data ProtectionKMS, S3 EncryptionAutomatedAWS Config✅

Section 500.03: Cybersecurity Policy

NYDFS ControlAWS ControlEvidence TypeCollection MethodStatus
500.03(a) - Policy FrameworkAWS OrganizationsManualPolicy Documentation✅
500.03(b) - Access ControlsIAM Password PolicyAutomatedAWS Config✅
500.03(c) - Business ContinuityAWS BackupAutomatedAWS Backup✅
500.03(d) - Vendor ManagementAWS Service CatalogManualVendor Assessment⚠️

Section 500.04: Chief Information Security Officer

NYDFS ControlAWS ControlEvidence TypeCollection MethodStatus
500.04(a) - CISO RoleAWS OrganizationsManualRole Documentation✅
500.04(b) - ReportingCloudWatch DashboardsAutomatedCloudWatch✅
500.04(c) - Risk AssessmentAWS Security HubAutomatedSecurity Hub✅

Section 500.05: Penetration Testing

NYDFS ControlAWS ControlEvidence TypeCollection MethodStatus
500.05(a) - Annual TestingAWS InspectorManualPenetration Test Report⚠️
500.05(b) - Vulnerability AssessmentAWS Security HubAutomatedSecurity Hub✅
500.05(c) - RemediationAWS Systems ManagerAutomatedSystems Manager✅

Evidence Collection Methods

Automated Collection

  1. AWS Config Rules

    • Compliance status
    • Configuration history
    • Resource relationships
  2. AWS Security Hub

    • Security findings
    • Compliance status
    • Risk scores
  3. CloudWatch Logs

    • Access logs
    • Security events
    • System metrics

Manual Collection

  1. Policy Documentation

    • Security policies
    • Procedures
    • Runbooks
  2. Assessment Reports

    • Penetration tests
    • Risk assessments
    • Vendor reviews

Control Implementation Status

pie title Control Implementation Status
    "Implemented" : 75
    "In Progress" : 15
    "Not Started" : 10

Key Metrics

MetricTargetCurrentStatus
Control Coverage100%85%⚠️
Automated Evidence80%75%⚠️
Critical Controls100%95%✅
High Risk Controls100%90%✅

Remediation Priorities

High Priority

  1. Complete vendor management program
  2. Finalize annual penetration testing
  3. Update business continuity documentation

Medium Priority

  1. Enhance automated evidence collection
  2. Implement additional AWS Config rules
  3. Update security policies

Low Priority

  1. Document manual processes
  2. Review and update runbooks
  3. Enhance reporting dashboards