Job Description
Role Purpose: What is the main purpose of the role? Why does the role exist? Describe the role in a way that distinguishes it from any other role. If applicable, describe the people management and geographical scope of the role (E.g. How many staff in country/cluster? How many locations/markets for which job holder is responsible? How many are in the team?).
This role serves as the designated security gate-keeper for IT change, ensuring that proposed changes to infrastructure, applications, networks, cloud environments, and identity systems are reviewed against security standards before approval. The specialist embeds security throughout the IT change lifecycle: challenging architectural design decisions, assessing endpoint and network security implications, reviewing cloud and identity control changes, and flagging insecure practices and tracking their remediation across the change lifecycle in coordination with the Change Risk Assessment (CRA) team. The specialist is expected to actively identify opportunities to leverage AI tooling to improve the consistency, coverage, and throughput of the security review function.
The role requires hands-on technical depth across endpoint, network, cloud, and identity security disciplines, enabling credible scrutiny of firewall rule sets, application traffic flows, cloud IAM configurations, and privileged access changes. The specialist must translate complex technical findings into clear, actionable risk guidance for engineering teams and executive stakeholders alike.
Key Responsibilities : What is the role accountable for and what are its key responsibilities? Describe the key result areas for this role specifically, rather than those for the team or role family where this role works.
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.
Qualifications
- Bachelor's degree in Computer Science, Information Security, or a related field (or equivalent practical
- 7+ years in information security with a primary focus on security architecture review, change governance, or technical security assurance.
- Working knowledge of security frameworks relevant to APAC financial services: ISO 27001, NIST CSF 2.0, CIS Controls v8, PCI DSS v4.0, MAS TRM (Singapore), APRA CPS 234 (Australia).
- Hands-on experience reviewing firewall rule sets across enterprise platforms (mainstream security tooling platform) — able to identify over-permissive rules, shadow rules, and lateral movement paths independently of vendor tooling.
- Demonstrated ability to trace and validate application secure traffic flows: TLS version and cipher validation, proxy/SSL inspection bypass analysis, load balancer SSL termination, API gateway mTLS, and certificate chain verification.
- Endpoint security experience with major EDR/XDR platforms — able to assess sensor coverage, detection policy scope, and agent deployment changes.
- Cloud security experience across at least one major provider (AWS, Azure, or GCP) — covering IAM policy review, security group/NSG analysis, CSPM tooling, cloud-native audit logging, and container/Kubernetes security controls.
- Identity and access management experience — reviewing IAM role assignments, PAM vaulting configurations, conditional access policies, MFA enforcement gaps, and non-human identity lifecycle controls in Active Directory and/or Entra ID environments.
- Experience working alongside a formal deviation/exception management function — flagging insecure practices, providing technical risk input to deviation assessments, and tracking remediation status through to closure without owning the formal exception process.
- Proven track record of escalating technical security risk to senior stakeholders with written risk communications consumable by non-technical decision-makers.
experience).
- Relevant certifications such as CISSP or CISM
- Firewall/network security vendor certification (Palo Alto PCNSE, Fortinet NSE 4/5, Check Point CCSE)
- Microsoft SC-200 (Security Operations Analyst) or MD-102 (Endpoint Administrator)
- CompTIA CySA+ or equivalent for threat analysis in a change review context
- Zero Trust or SD-WAN certification