55AA-021

Security Baselines, Compliance, and Automation

Level
Graduate
Status
Under development

Note: this course is still being designed and calibrated; the page content is for reference and does not represent the final teaching version.

Syllabus

Course Overview

Security Baselines, Compliance, and Automation turns security requirements into executable, auditable, and sustainable engineering processes. Topics include baseline modeling, policy as code, configuration scanning, evidence collection, vulnerability management, exception handling, and automated remediation.

This is the applied security-engineering course after software engineering, system security, operating systems, and applied cryptography.

Prerequisites

  • Software engineering and system-security fundamentals.
  • Familiarity with Linux, scripting, CI, and configuration files.
  • Understanding of basic cryptography, identity, and logging concepts.

Learning Outcomes

  • Decompose security requirements into testable controls.
  • Express configuration and compliance rules as policy as code.
  • Collect evidence automatically and generate audit reports.
  • Manage vulnerabilities, exceptions, risk acceptance, and remediation SLAs.
  • Build a maintainable automation pipeline for security baselines.

Course Format

  • Two meetings per week: one for core concepts and one for labs, paper discussion, or project review.
  • The course proceeds over 16 weeks, each with a checkable assignment, lab, or project milestone.
  • Reproducibility is required: code, configuration, data, lab logs, and reports must be reviewable by staff or peers.

Weekly Plan

Week 2

Security controls, baselines, and risk: lab and review

Convert requirements into controls and test points. Complete the paired lab, record issues, and explain design tradeoffs in class review.

Week 4

Linux, cloud, and application baselines: lab and review

Write configuration-check scripts. Complete the paired lab, record issues, and explain design tradeoffs in class review.

Week 6

Policy as code: lab and review

Express rules with OPA, Rego, or equivalent tools. Complete the paired lab, record issues, and explain design tradeoffs in class review.

Week 8

CI/CD security gates: lab and review

Integrate scans and policy checks into pipelines. Complete the paired lab, record issues, and explain design tradeoffs in class review.

Week 10

Evidence collection and audit trails: lab and review

Design automated evidence packages and report formats. Complete the paired lab, record issues, and explain design tradeoffs in class review.

Week 12

Vulnerability management and exception workflow: lab and review

Create priority, SLA, and risk-acceptance records. Complete the paired lab, record issues, and explain design tradeoffs in class review.

Week 14

Automated remediation and drift detection: lab and review

Implement one automated security-configuration fix. Complete the paired lab, record issues, and explain design tradeoffs in class review.

Week 16

Compliance automation project: lab and review

Submit baseline tooling, evidence package, and runbook. Complete the paired lab, record issues, and explain design tradeoffs in class review.

Assessment

Individual assignments

Concept questions, reading responses, design tasks, and small programming or lab exercises.

25%
Labs and project

Policy rules, scan pipelines, evidence packages, and remediation workflow.

40%
Participation and review

Participation in discussions, demos, code or paper reviews, and peer feedback.

10%
Final report and defense

Submit reproducible artifacts, a technical report, and a demo explaining methods, results, limitations, and future work.

25%

Course Project

Students build baseline automation for a service, host, container, or cloud resource set, including rules, scanning, evidence, exceptions, and remediation guidance.

Policies

  • AI tools are allowed, but generated code, lab notes, and design suggestions must be reviewed by the student and disclosed in the report.
  • Students may not submit code, proofs, configuration, or experimental results they cannot explain; each member must defend their own design, tests, and tradeoffs.
  • Late work affects iteration grades, but the course values reproducible, auditable, and maintainable results over last-minute accumulation.

Reference Courses