Skip to content
IT Atlas

Information Technology · itatlas.ai

The reference layer for Information Technology.

IT Atlas explains how enterprise IT actually fits together, addressing and routing, directories and tokens, hypervisors and landing zones, detection and recovery, as one connected structure rather than a list of products. Vendor neutral, technically precise, and written for the people who operate and design these environments.

  • Standards aligned
  • Vendor neutral
  • Defence oriented
  • Practitioner written
A stacked diagram of the enterprise IT estate, from Endpoints at the base up through Network, Identity, Compute and Virtualization, Cloud and Data to Enterprise at the top.
One estate, seven dependent tiers: work happens at the top, and every tier below it is a dependency you either designed deliberately or inherited by accident.
163
Topic articles

Across twelve layers of the estate

158
Reference entries

Glossary, protocols, technologies and frameworks

17
Guided routes

Learning paths and troubleshooting flows

380 indexed entries across topics, glossary, protocols, technologies and frameworks.

One connected system

A single question travels through the atlas in one direction. Each stage links to the next, so you never end up with a definition and no idea what to do with it.

The enterprise IT stack

Operational Technology has the Purdue model. Information Technology has no single canonical diagram, so IT Atlas uses this one: seven dependency tiers that every article is filed against. Select a tier to see what lives there, what it relies on, and how it typically fails.

T5The real control plane

Identity & access

Directories, authentication, tokens, conditional access, privileged access and lifecycle joiner mover leaver processes. In a cloud era estate, identity, not the firewall, is the perimeter, and identity compromise is the shortest path to everything above and below it.

What lives here

Directory servicesSingle sign-onMulti factor authenticationConditional accessPrivileged access
Depends on
Network reachability and a trusted device signal
Typical failure
Standing privilege, legacy authentication left enabled, or a token stolen after MFA has already passed.

Read next

Where are you today?

Six starting points, by the work you are actually doing.

New to IT

You know the words but not how they connect, and you want the model before the products.

Support & service desk

You are diagnosing something now and need a structured path rather than a forum thread.

Infrastructure & network

You are designing or changing addressing, routing, virtualisation or storage.

Security & identity

You are reducing exposure, tightening identity, or evidencing controls.

Architecture & strategy

You are choosing a target state and need the trade offs stated plainly.

Leadership & governance

You are accountable for risk, spend and compliance rather than configuration.

The lifecycle the atlas supports

Fourteen stages from first inventory to continuous improvement. Most environments are strong in a few and silent in the rest.

  1. 01DiscoverEnumerate assets, identities, data and dependencies.
  2. 02ClassifyRank systems and data by business impact.
  3. 03BaselineRecord the current configuration and its gaps.
  4. 04AssessMeasure against a chosen framework, not a feeling.
  5. 05DesignChoose a target architecture and state the trade offs.
  6. 06SegmentDecide what may reach what, and enforce it.
  7. 07HardenApply configuration baselines and remove standing privilege.
  8. 08ImplementDeploy as code, with change control and rollback.
  9. 09MonitorCollect telemetry that answers real questions.
  10. 10DetectTurn telemetry into rules, coverage and alerts.
  11. 11RespondContain, eradicate and communicate under a tested plan.
  12. 12RecoverRestore from protected backups within agreed objectives.
  13. 13ReviewRun blameless post incident and post change reviews.
  14. 14ImproveFeed findings back into design and baselines.

The layers of an IT environment

Every article in IT Atlas sits in one of these sections. Follow the dependencies downward when designing, and upward when troubleshooting.

IT Fundamentals

Start here

The vocabulary, layers and mental models that everything else in IT Atlas builds on.

Concepts · Comparisons · Models

Infrastructure

Compute, storage, resilience

Servers, virtualization, storage, data centres, backup, high availability and disaster recovery, the physical and virtual foundation everything else runs on.

Servers · Virtualization · Storage · Data Centers

Cloud

Platforms and service models

Service models, hyperscale platforms, cloud networking, identity, governance and cost management, explained by architecture rather than by product catalogue.

Cloud Fundamentals · Azure · AWS · Google Cloud

Networking

How systems reach each other

Addressing, routing, switching, name resolution, segmentation, remote access and the protocols that carry enterprise traffic.

Fundamentals · Protocols · Routing & Switching · Segmentation

Security

A layer, not a silo

Security architecture, Zero Trust, detection and response, vulnerability and patch management, monitoring and incident handling across every other layer.

Security Architecture · Zero Trust · Detection & Response · Security Operations

Identity

The modern control plane

Directories, identity providers, authentication and authorization protocols, conditional access, privileged access and identity governance.

Directories · Authentication · Authorization · Federation

Endpoints

Devices and their lifecycle

Operating systems, device management, enrolment, configuration, compliance and the full procure to retire endpoint lifecycle.

Operating Systems · Endpoint Management · Mobile · Compliance

Applications & Data

What the business actually uses

Enterprise applications, SaaS, APIs, databases, analytics platforms, collaboration and the data they create and consume.

Enterprise Applications · SaaS · APIs & Integration · Databases

Operations

Keeping the environment healthy

IT operations, service management, monitoring and observability, asset management, automation and documentation.

IT Operations · Service Management · Monitoring · Asset Management

Governance

Direction, policy and risk

IT governance, policy hierarchies, risk management, access and data governance, vendor management and compliance.

IT Governance · Policy · Risk · Data Governance

Platforms

Ecosystems in context

Vendor ecosystems explained structurally: what each service does, where it sits, and how the pieces depend on one another.

Microsoft 365 · Microsoft Security · Vendor Ecosystems

Architecture

Reference designs

Reference architectures and architectural patterns for networks, identity, security, cloud and resilience.

Enterprise Architecture · Network Architecture · Identity Architecture · Security Architecture

Start here

Foundational articles that most other topics reference.

Reference desks

IT is not OT

The two domains share vocabulary and almost nothing else. IT Atlas covers Information Technology only; Operational Technology has its own platform.

Information Technology compared with Operational Technology
DimensionInformation TechnologyOperational Technology
Priority orderConfidentiality, integrity, then availabilitySafety and availability, then integrity, confidentiality last
Consequence of failureData loss or disclosure, outage, financial and reputational harmPhysical harm, environmental release, equipment damage, lost production
Asset lifetime3, 7 years, SaaS changes continuously10, 30 years, often past vendor support
PatchingRoutine and automated on monthly cyclesRare, vendor validated, scheduled around plant outages
ProtocolsTCP/IP, HTTPS, DNS, Kerberos, SAML, OIDC, SMB, LDAPModbus, DNP3, PROFINET, OPC UA, IEC 61850, CIP
TestingAuthenticated scanning and penetration testing are standardActive scanning can fault controllers; passive monitoring is the default
Dominant frameworksNIST CSF, CIS Controls, ISO 27001, ITIL, ATT&CK EnterpriseIEC 62443, NIST SP 800-82, ATT&CK for ICS, Purdue model

How IT Atlas is written

The IT Atlas and RWP Ventures marks joined by a glowing arc under the line Connected by purpose: knowledge, execution, greater impact.

Reference material, not sales content.

Nothing here is ranked, scored, sponsored or recommended. Products are described by the function they perform, standards are cited as primary sources, and common failure modes are treated as first class content because that is where practitioner time actually goes. Where a simplification would mislead, the article states the real behaviour instead.

Editorial principles
Scope
Information Technology only, across twelve layers of the estate.
Method
Structured data with typed fields, so every article states what it depends on.