Security

Security built into the
infrastructure layer.

Security considerations extend across facilities, networks, platforms, access management, data and operations. AALTA approaches these as connected layers of infrastructure architecture.

Layered Security Architecture

Six layers. One security architecture.

No single control carries the system. Security considerations span the physical environment, infrastructure connectivity, platform configuration, access management, data handling and ongoing operations.

No single control carries the system. Layers reinforce one another.

Physical & Infrastructure Layers

Security begins with the environment.

01 / Facility

The physical environment matters.

Facility-level security considerations form the physical foundation of infrastructure protection. Site characteristics, access requirements and operational boundaries must be considered when defining a deployment.

Physical environment

Facility access requirements

Infrastructure boundaries

Operational controls

02 / Network

Controlled infrastructure connectivity.

Network architecture establishes the connectivity and separation requirements of dedicated compute environments. Network configuration should reflect the workload, operational model and customer security requirements.

Network architecture

Connectivity boundaries

Traffic separation requirements

Infrastructure integration

03 / Platform

Security at the compute layer.

Platform configuration is part of the broader security architecture. Infrastructure deployment and configuration must account for the intended workload and its operational requirements.

Platform configuration

Compute environment boundaries

Deployment configuration

Operational requirements

Access & Data

Define who has access.
Define where data belongs.

Identity

Access is an architectural decision.

Identity and access requirements should be defined around the customer environment, including who can access infrastructure resources and how administrative responsibilities are assigned.

Access requirements

Administrative roles

Customer environment boundaries

Responsibility assignment

Data

Data requirements shape
infrastructure design.

Data handling, location and access requirements influence how dedicated infrastructure environments are configured and operated.

Data locality

Access boundaries

Storage requirements

Customer-defined policies

Operations

Security is an ongoing operational consideration.

Infrastructure security extends beyond initial deployment. Operational requirements, maintenance responsibilities and procedures must be considered throughout the infrastructure lifecycle.

01Deployment
02Configuration
03Operations
04Maintenance

Operational procedures

Infrastructure monitoring requirements

Maintenance coordination

Change management considerations

Responsibility Model

Security responsibilities should be clearly defined.

Dedicated infrastructure environments involve responsibilities across infrastructure providers and customers. The allocation of specific controls depends on the services selected and the deployment agreement.

Security Area

AALTA Scope

Customer Scope

To Be Defined

Facility

Scope to confirm

Customer-defined requirements

Shared scope to define

Network

Scope to confirm

Customer-defined requirements

Shared scope to define

Platform

Scope to confirm

Customer-defined requirements

Shared scope to define

Identity

Scope to confirm

Customer-defined requirements

Shared scope to define

Data

Scope to confirm

Customer-defined requirements

Shared scope to define

Operations

Scope to confirm

Customer-defined requirements

Shared scope to define

Final responsibility boundaries depend on the selected services and contractual scope.

Compliance Considerations

Security requirements need clear evidence.

Customer security and compliance requirements should be reviewed during infrastructure planning to determine the applicable controls, supporting documentation and responsibilities for the proposed deployment.

01 / Security Requirements

Define the security requirements relevant to the proposed environment.

02 / Control Responsibilities

Identify how applicable responsibilities are allocated across the deployment.

03 / Supporting Documentation

Determine what documentation and evidence are available or required for evaluation.

Security Principles

No single control
carries the system.

Facility, network, platform, identity, data and operational considerations reinforce one another within the overall infrastructure architecture.

FACILITY

NETWORK

PLATFORM

IDENTITY

DATA

OPERATIONS

Security Requirements

Let's discuss your infrastructure requirements.

Share the security, access and operational requirements of your deployment so the relevant infrastructure scope can be evaluated.

Talk to Our Teamai@aalta.ai