| 1 | Security Change Review & Gate Enforcement - Review all IT change requests with a security impact classification (standard, significant, or emergency) using a structured methodology covering attack surface expansion, data exposure, authentication and authorisation changes, cryptographic controls, network connectivity, cloud and identity configuration, and third-party dependencies.
- Issue security approval, conditional approval (specifying mandatory compensating controls and evidence closure requirements), or rejection to the CAB with written technical justification.
- Track open security conditions on conditionally approved changes to verified closure before production deployment.
- Apply security review checklists consistently across change types: infrastructure, application, network, cloud, and identity.
- Use AI-assisted pre-screening tools to perform an initial triage of incoming change requests against security policy.
- Flagging high-risk changes for prioritised human review and filtering low-risk routine changes for expedited processing.
|
| 2 | Architecture Challenge & Security Scrutiny - Evaluate proposed architecture diagrams, HLD/LLD documents, data flow diagrams, and topology changes for security design weaknesses before change approval.
- Conduct threat modelling (STRIDE, PASTA, or attack tree as appropriate) on significant changes to surface threat actors, attack vectors, and control gaps.
- Challenge architects and engineers on violations of defence-in-depth, least privilege, zero-trust, and secure-by-default principles — providing specific, evidence-based counter-proposals rather than generic objections.
- Require resolution of implicit security assumptions (undocumented firewall rules, assumed TLS enforcement, assumed patch state) before sign-off.
|
| 3 | Network Security Review - Review firewall change requests at rule-set level: validate least-privilege source/destination/service scope, identify rules enabling lateral movement, and confirm alignment with network segmentation policy across mainstream security tooling environments.
- Trace application traffic flows end-to-end (client → proxy/load balancer → application tier → database/API → external service) to verify TLS 1.2+/1.3 enforcement, on-path inspection (IDS/IPS, SSL decryption, web proxy, CASB), and preservation of segmentation boundaries.
- Assess VLAN, micro-segmentation, SD-WAN policy, and remote access (IPSec VPN, SSL VPN, ZTNA) changes for security implications.
- Verify management-plane, DNS, and NTP change requests to prevent covert channels, DNS tunnelling, or bypass of monitoring controls.
|
| 4 | Endpoint Security Review - Assess endpoint security posture impact of proposed changes — including EDR/XDR sensor coverage gaps (mainstream endpoint security tools), DLP policy continuity, NAC compliance posture, and application allowlist integrity.
- Review changes involving endpoint agent installation, removal, or policy modification against the endpoint security baseline; identify changes that reduce telemetry visibility or create sensor blind spots.
- Evaluate mobile device and BYOD changes to confirm MDM and MAM policy enforcement is maintained or formally compensated.
|
| 5 | Cloud Security Review - Review proposed cloud infrastructure changes (AWS, Azure, GCP) for misconfiguration risk: IAM policy over-permission, publicly exposed storage (S3 buckets, Blob containers), unencrypted data at rest (KMS/CMK policy gaps), missing VPC/NSG controls, and absent or incomplete audit logging (CloudTrail, Azure Monitor/Defender for Cloud, GCP Cloud Audit Logs).
- Assess cloud network security controls — security groups, network ACLs, private endpoints, service endpoints, and cloud-native firewall policies — with the same rigour applied to on-premises firewall reviews.
- Evaluate container and Kubernetes workload changes: image provenance and scan status, pod security admission controls, service mesh mTLS enforcement, and secrets management (Mainstream key/secrets management solution).
- Review SaaS application onboarding for OAuth scope over-permission, SSO integration completeness, data residency compliance, and CASB policy coverage.
- Validate that Cloud Security Posture Management (CSPM) tooling maintains coverage across new cloud accounts or subscriptions introduced by a change.
|
| 6 | Identity & Access Security Review - Review identity and access changes for security risk: new privileged role assignments, service account creation, federated trust relationships (SAML 2.0, OIDC/OAuth 2.0), and conditional access or Group Policy Object (GPO) modifications.
- Assess Privileged Access Management (PAM) implications — confirm that privileged accounts use just-in-time (JIT) access, are vaulted (PAM tools), and that no standing privileged access is introduced without compensating controls.
- Evaluate Active Directory and Entra ID (Azure AD) changes — OU structure, trust relationships, RBAC assignments — for privilege escalation paths.
- Confirm MFA enforcement for all access paths introduced by a change, including API keys, service principals, and machine/workload identities.
- Verify that non-human identities (service accounts, managed identities, workload identities) created by changes follow least-privilege and credential rotation policies.
|
| 7 | Security Risk Tracking & Continuous Improvement - Flag security weaknesses, non-compliant configurations, and insecure practices identified during change reviews to the relevant project team and the Change Risk Assessment (CRA) team for formal deviation or exception handling — this role does not own the deviation process.
- Maintain a security findings tracker recording: the change or project, the specific insecure practice identified, the risk rating, the flagging date, the recommended remediation, and the status.
- Follow up on flagged items in subsequent related changes — confirm that previously identified weaknesses have been addressed before approving dependent changes.
- Identify patterns of recurring insecure practices across change submissions and escalate systemic issues to the Head of Technical Security, APAC for policy or standards remediation rather than case-by-case correction.
- Contribute findings and lessons learned to the CRA team and security standards owners to drive improvement in future change design.
|
| 8 | Escalation Management - Apply defined escalation criteria: security risks irresolvable within the change window, project team/security disagreements, emergency changes with compressed review timelines, and changes setting risk-negative precedent.
- Produce escalation briefs stating the specific technical risk, affected asset or system, business impact of proceeding versus deferring, recommended path, and consequence of each option — enabling executive decision without requiring technical depth from the approver.
- Own escalated items through to decision and verified implementation of agreed outcomes.
|
| 9 | Stakeholder Engagement & Risk Communication - Articulate technical security findings in language calibrated to the audience — quantified business impact for executives, specific remediation guidance for engineers, and policy/regulatory framing for compliance stakeholders.
- Facilitate security review sessions with architects, cloud engineers, platform engineers, developers, and infrastructure teams — challenging proposals through technical depth rather than policy reference.
- Produce written security review outputs (change assessment reports, deviation forms, CAB security memos, escalation briefs) that are precise, concise, and audit-ready.
- Maintain a knowledge base of security assessment decisions and precedents to accelerate future reviews and reduce recurrence of common weaknesses.
|
| 10 | Security Policy & Standards Development - Contribute to the development and maintenance of security review checklists, network segmentation standards, endpoint baselines, cloud security guardrails, and identity governance guidelines.
- Feed recurring weakness patterns from change reviews back to policy and standard owners for systemic remediation.
|
| 11 | AI-Augmented Review & Process Automation - Identify security review sub-processes that are repetitive, rule-based, or pattern-driven and suitable for AI or automation — including firewall rule validation against segmentation policy, Infrastructure-as-Code (IaC) template misconfiguration scanning (Terraform, CloudFormation, Bicep), certificate and cryptographic configuration checks, and IAM over-permission detection.
- Work with security tooling and engineering teams to implement, test, and maintain those automations — defining the scope of automation, required human validation checkpoints, and handling of AI-generated false positives.
- Evaluate AI-generated security review outputs critically: validate findings before acting, recognise model limitations in context-specific judgements (business justification, risk appetite), and ensure AI augmentation does not create false assurance.
- Assess emerging AI security tools — LLM-based configuration and code review assistants, AI-native CSPM and SIEM co-pilots, NLP-based pattern detection across change history — for fit within the change review function and recommend adoption where quality or throughput improvement is demonstrable.
- Maintain documentation of all AI-assisted review processes covering scope, known limitations, human oversight checkpoints, and validation approach — ensuring the process is transparent, repeatable, and auditable.
|