Security Architect
-
IT/Tech
Job Description & How to Apply Below
The Security Architect designs the security controls, patterns and reference architectures that systems must follow, reviews solutions and changes against them, and advises on risk treatment. They translate policy and framework requirements into technical standards engineers can build to.
IT service delivery
What you ownThe Security Architect designs the security controls, patterns and reference architectures that systems must follow, reviews solutions and changes against them, and advises on risk treatment.
- Define security architecture principles, patterns and reference designs
- Review solution designs, changes and vendors against security standards
- Translate framework and policy requirements into technical controls
- Lead threat modeling and architecture risk assessments
- Advise on identity, network, cloud and data protection design
- Track architecture exceptions and remediation roadmaps
- Keep standards current with emerging threats and technologies
Who this role reports to, who reports to them, and the peers they work with most.
Reports toChief Information Security Officer
Works closely with- Security Analyst
- IT Compliance Manager
- IT Risk Manager
- Engineering Manager
- Change and Release Manager
- Dev Ops Engineer
The Security Architect sets the patterns and reference designs that systems must follow and answers to the CISO and CTO for whether engineering actually builds to them. Smart Suite holds the standards, the exceptions and the reviews as linked records against the CMDB, so control coverage by system is shown rather than asserted.
Own the standards, patterns and exceptions Reference patterns engineers can be held toSecurity standards and reference patterns are kept in the Control Framework & Regulatory Libraries as controls mapped to NIST CSF, ISO 27001 and CIS, so a pattern is a control with a framework reference, not a wiki page nobody can test against.
No exception quietly becomes permanentEvery architecture exception records its owner, expiry date, compensating control and remediation roadmap, and the dashboard shows which are approaching expiry. An exception cannot drift into the permanent estate, because the record will ask about it.
Which pattern is failing in practiceThreats identified in your architecture risk assessments are captured in Cyber Threat Management and linked to the vulnerabilities, incidents and controls that concern them, so the Security Analyst's findings show up against the threat you assessed and root cause analysis tells you which pattern is failing in practice.
Review designs and changes with engineering and change management Findings recorded against the change, not emailedSolution designs and significant changes route through security review inside the change workflow, with your findings recorded against the change itself. The Change and Release Manager cannot schedule what you have not cleared, and your findings travel with the CAB record.
Controls mapped to systems, not to diagramsThe asset register and Configuration Management (CMDB) tell you which systems, applications and dependencies a design touches, so review scope is derived from the inventory and controls are mapped to the systems they protect, not to a diagram from last year.
Engineering and Dev Ops answering in the recordIn-record conversations, mentions and emails bring the Engineering Manager and Dev Ops Engineer into the review where the finding lives, so clarifications, pushback and the agreed fix are on the record and not spread across three channels.
Report coverage and exceptions to the CISO and CTO Control coverage by system on one dashboardReview throughput, open exceptions and control coverage by system are live, so the CISO sees where the estate meets the standard and where it does not. Risk-based prioritization ranks the gaps by inherent risk and business dependency.
Framework evidence from the same mappingBecause patterns are controls mapped to NIST CSF, ISO 27001 and CIS, the IT Compliance Manager's framework evidence and the IT Risk Manager's risk linkage come from your mapping. One set of standards serves design review, audit and risk.
Standards kept current with a version historyStandards, tests and documented processes carry version history and audit trails, so when a pattern changes for a new threat or a post-quantum migration, who approved it and what it replaced are recorded. Engineering builds to the current version.
Security. Holds…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).
View / Apply for Jobs
Matching My Jurisdiction