This curriculum spans the integration of security practices across IT service management processes, comparable in scope to a multi-workshop program that aligns security controls with service lifecycle phases, operational workflows, and compliance requirements within a regulated enterprise environment.
Module 1: Integrating Security into Service Lifecycle Management
- Define security requirements during service design by aligning with ISO/IEC 27001 controls and mapping them to specific service components.
- Embed security checkpoints in each phase of the ITIL service lifecycle, ensuring change advisory board (CAB) reviews include risk impact assessments.
- Coordinate between security teams and service owners to validate that disaster recovery plans include cryptographic key escrow and access reactivation procedures.
- Implement mandatory security sign-offs for service validation and testing, requiring documented evidence of penetration test results and vulnerability scans.
- Establish criteria for when a service transition must be halted due to unresolved high-risk vulnerabilities in third-party dependencies.
- Integrate security metrics such as mean time to detect (MTTD) and mean time to respond (MTTR) into service reporting dashboards.
Module 2: Identity and Access Governance in Service Operations
- Design role-based access control (RBAC) models that reflect service ownership hierarchies and align with least privilege principles across ITSM tools.
- Enforce automated deprovisioning workflows triggered by HR system updates, with audit trails retained for SOX or GDPR compliance.
- Implement just-in-time (JIT) access for privileged service accounts, requiring multi-factor authentication and time-bound approvals.
- Configure access review cycles within the ITSM platform to validate standing entitlements for critical services every 90 days.
- Negotiate access certification responsibilities between service managers and data owners when segregation of duties (SoD) conflicts arise.
- Integrate privileged access management (PAM) systems with incident and problem management to correlate privileged session logs with service disruptions.
Module 3: Threat-Informed Vulnerability Management
- Prioritize patching schedules based on exploit availability, asset criticality, and service dependency maps from the CMDB.
- Establish thresholds for acceptable risk exceptions, requiring CISO approval when critical systems remain unpatched beyond 30 days.
- Automate vulnerability ingestion from scanning tools into the ITSM system, triggering incident records for confirmed exploitable findings.
- Coordinate maintenance windows with business units to minimize service disruption during emergency patch deployments.
- Define SLAs for vulnerability remediation that vary by CVSS score and service classification (e.g., Tier 0 vs. Tier 2).
- Conduct tabletop exercises simulating zero-day exploits to test patch deployment coordination between security and operations teams.
Module 4: Security Event Correlation and Incident Response
- Map SIEM alert categories to ITSM incident templates, ensuring consistent classification and routing to appropriate support tiers.
- Implement automated incident creation from EDR platforms with enriched context such as process trees and lateral movement indicators.
- Define escalation paths that trigger cross-functional war rooms when incidents impact multiple services or violate regulatory timelines.
- Integrate incident timelines with service outage records to distinguish security-driven outages from infrastructure failures.
- Enforce mandatory root cause analysis (RCA) documentation for security incidents, linking findings to problem management records.
- Configure bi-directional sync between the ITSM incident module and threat intelligence platforms to enrich tickets with IOCs.
Module 5: Secure Change and Configuration Management
- Require security impact assessments for standard, normal, and emergency changes, with automated checks against baseline configurations.
- Implement pre-change vulnerability validation using automated scans to prevent deployment of non-compliant builds.
- Restrict emergency change approvals to designated security and operations leads, with post-implementation review deadlines set at 72 hours.
- Integrate configuration management database (CMDB) health checks into the change process to ensure asset records reflect deployed security controls.
- Enforce digital signatures for change implementation scripts to prevent tampering during deployment.
- Track rollback success rates for security-related changes to assess stability impact and refine future deployment strategies.
Module 6: Third-Party and Supply Chain Risk in Service Delivery
- Require third-party service providers to submit SOC 2 Type II reports and undergo annual security assessments as contract renewal conditions.
- Map vendor-provided services to the organization’s risk register, assigning ownership for monitoring control effectiveness.
- Implement contract clauses mandating notification of security incidents within four hours of detection.
- Integrate vendor risk scores into the service catalog, flagging high-risk components in service design documentation.
- Conduct joint incident response drills with critical suppliers to validate communication and containment protocols.
- Enforce segregation of vendor access using dedicated network zones and jump hosts monitored by the organization’s SIEM.
Module 7: Security Metrics, Audits, and Continuous Improvement
- Define and track key risk indicators (KRIs) such as percentage of unpatched critical assets and failed access reviews per service.
- Prepare for internal and external audits by maintaining immutable logs of access changes, incident responses, and CAB decisions.
- Conduct annual control effectiveness reviews using sample testing of ITSM records to validate compliance with NIST SP 800-53.
- Align security performance data with service level agreements (SLAs) to identify services with recurring security delays.
- Implement feedback loops from post-incident reviews into service improvement plans (SIPs) with assigned accountability.
- Use heat maps to visualize service-specific risk exposure over time, supporting executive decision-making on investment priorities.
Module 8: Security Awareness and Role-Specific Training in ITSM
- Develop scenario-based training modules for service desk analysts on identifying and escalating social engineering attempts.
- Customize phishing simulation campaigns based on user roles, targeting high-risk groups such as change managers and DBAs.
- Embed security decision checkpoints in standard operating procedures (SOPs) for common tasks like password resets and access grants.
- Measure training effectiveness through metrics such as reduction in误-click rates and faster incident reporting times.
- Assign mandatory annual security refreshers within the learning management system (LMS), tied to role-based access renewals.
- Collaborate with HR to integrate security conduct into performance evaluations for ITSM personnel.