top of page

I Manage Security Controls. But I’m Called a Security Architect

Updated: Apr 30

My title says Security Architect. My work says something else.

I configure IAM, define policies, run scans, respond to vulnerabilities. This is critical work.

But is this architecture?


Why Do I Believe I’m an Architect?

  • I hold security certifications

  • I design access policies and controls

  • I run audits and compliance checks

  • My role is titled “Security Architect”


What this actually means - I operate strongly in P5 (implementation) and P6 (operations/governance).


What I Actually Do

  • Configure IAM / access controls

  • Define encryption / key management

  • Run vulnerability scans

  • Monitor incidents and compliance


All essential. But structurally:

This is implementation and operations.


        Want to read more?

        Subscribe to architecturerating.com to keep reading this exclusive post.

        Enterprise Intelligence

        Transforming Strategy into Execution with Precision and Real Intelligence

        bottom of page