Glossary
IT glossary: the key terms
Clear definitions of the concepts that structure today's IT system mapping, regulatory compliance and cybersecurity.
-
Application mapping
Application mapping is the practice of recording an organization's applications, who answers for them, and what connects them: data flows, databases, servers. It shows what depends on what before a change, an incident or an audit.
-
ArchiMate
ArchiMate is an open and independent modeling language for enterprise architecture, published as a standard by The Open Group. It provides element types, relationships and a graphical notation to describe an organization, its applications and its infrastructure in a single model.
-
Architecture document
An architecture document describes how an IT solution is built and hosted: components, servers, network, data flows, security and operations. It is written during the project, approved before go-live, and then used as the reference by the people who run, audit or change the solution.
-
BCP and DRP
A business continuity plan (BCP) describes how an organization keeps its essential activities running during a disruption and then restores them. A disaster recovery plan (DRP) is the part that brings the affected systems back into service, usually at an alternate site.
-
C4 model
The C4 model is an approach to diagramming software architecture, created by Simon Brown. It describes a software system through four nested levels of diagrams, from the most general to the most detailed: system context, containers, components and code.
-
CMDB
A CMDB (Configuration Management Database) is a centralised database that lists an organization's IT assets and their relationships. It is at the heart of IT mapping and ITSM governance.
-
Data flow mapping
Data flow mapping is the practice of recording and drawing the exchanges inside an IT estate: which application or machine sends what to which other, over which path and for what need. It combines a record of flows with the diagrams that show them, kept current over time.
-
HLD vs LLD
A high-level design (HLD) describes the overall architecture of a solution: its building blocks, zones and principles. A low-level design (LLD) takes the same solution down to the detail needed to build it: host names, addressing, VLANs, settings and firewall rules.
-
IT architecture
IT architecture is the organized description of an organization's information systems: the business activities they serve, the applications that support them, the data they exchange and the infrastructure that hosts them. The term also names the discipline that decides how those parts fit together and where they should go next.
-
IT asset inventory
An IT asset inventory is the maintained list of the components an organization runs or relies on (hardware, software, services, data), each with a description, a location and an owner. It answers the question of what you have, before any mapping or risk analysis.
-
IT impact analysis
An IT impact analysis establishes what stops or degrades when a component of the infrastructure fails, changes or is removed. It follows the dependency chain from the machine to the applications, the business activities and the people who need to be told.
-
IT system mapping
IT system mapping is the structured description of the components of an organization's information system and of the dependencies between them, from business process down to network device. It combines an inventory of those components with views that connect them, each view built to answer a specific question.
-
IT urbanization
IT urbanization is the French-rooted name for planning how an organization's applications and infrastructure evolve, the way a city is planned: a functional zoning plan and shared rules for every project. English speakers call the same practice enterprise architecture and application landscape rationalization.
-
Network flow matrix
A network flow matrix is a table of the network communications a system needs: the source, destination, protocol, port, direction and justification of each flow. It is the reference firewall rules are written from, and the reference they are later reviewed against.
-
NIS2
NIS2, Directive (EU) 2022/2555 of December 14, 2022, sets cybersecurity rules for so-called essential and important entities in eighteen sectors. It requires them to meet governance, risk-management and incident-reporting obligations.
-
ReCyF
ReCyF (Référentiel Cybersécurité France) is the framework published by ANSSI that structures the cybersecurity requirements applicable to essential and important entities under NIS2. It breaks down about twenty concrete objectives, audited against a maturity scale.
-
Software obsolescence
Software obsolescence is the state of software its vendor no longer maintains: it stops receiving fixes, security patches included, and support. It is dated version by version, from the end-of-support dates vendors publish.
-
Technical debt
Technical debt is the work an IT organization has postponed and will have to do eventually: an upgrade, a dependency to document, a workaround to replace. Until that work is done, every change costs more and takes longer.
-
TOGAF
The TOGAF Standard is a standard of The Open Group, described as an enterprise architecture methodology and framework. It sets out how to run architecture work, from the initial vision to governing the implementation, and prescribes neither a tool nor a notation.