IAM Security Architect

About the role

The IAM Security Architect designs and governs identity and access management security architectures that protect Ball Corporation’s enterprise environments while enabling business operations, digital transformation, and manufacturing reliability.

Key responsibilities

• Develop and maintain IAM solution architectures aligned to enterprise security strategy, principles, and reference architectures.
• Define and enforce IAM architecture patterns for workforce identity, partner access, service identities, and application access.
• Establish secure‑by‑design patterns for authentication, authorization, identity lifecycle management, and access governance (joiner/mover/leaver processes).
• Design and govern privileged access management architectures, including privileged identity controls, administrative pathways, and session governance.
• Provide architecture guidance and design oversight for IAM projects and programs, ensuring consistent implementation of identity security requirements.
• Participate in technology evaluations and architecture reviews for IAM capabilities to ensure alignment with enterprise standards and risk management goals.
• Partner with IT, application owners, and business stakeholders to embed IAM architecture into transformation, modernization, cloud adoption, and M&A initiatives.
• Collaborate with Cybersecurity Defense Operations to ensure IAM architectures support monitoring, detection, and response through appropriate logging and alerting.

Required profile

• Works under the direction of the Senior Manager of Identity & Access Management.
• Provides hands‑on architectural leadership for identity services, authentication, authorization, privileged access, identity lifecycle, and access governance.
• Ensures designs are scalable, interoperable, operationally sustainable, and measurable.

Required skills

• IAM solution architecture
• Privileged Access Management (PAM) design
• Authentication and authorization mechanisms
• Identity lifecycle management
• Access governance processes (joiner/mover/leaver)
• Secure‑by‑design pattern implementation