Software Technologies Inventory and Attributes on The International Foundation for Information Technology (IF4IT)

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

About This Inventory

The Software Technologies Inventory is the authoritative record of the software technologies an enterprise procures, deploys, operates, or depends upon. A single Noun Instance in this inventory is one discrete, governable software technology — a database engine, a language runtime, a container platform, an observability tool — identified, versioned, owned, and tracked through its lifecycle. It governs the technology layer that applications are built on and run within, which distinguishes it from the Applications Inventory that sits above it and the Vendors Inventory that supplies it.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

The following terms are used throughout this document with specific meanings. Terms defined in the IF4IT Enterprise Inventory Management Best Practices document or in discipline-specific Best Practices documents (APM, TPM, etc.) are not duplicated here — refer to those documents for broader inventory governance and discipline-specific vocabulary.

Term	Abbreviations and Acronyms	Definition
Common Vulnerabilities and Exposures	CVE	A publicly catalogued, uniquely identified security vulnerability affecting a specific software technology and version range.
End of Life	EOL	The point at which a supplier ceases to develop, sell, or maintain a software technology in any form.
End of Support	EOS	The point at which a supplier ceases to provide fixes, patches, or security updates for a software technology, whether or not it remains installed and running.
Middleware		Software technology whose purpose is to connect other software technologies, applications, or systems, carrying messages, transactions, or data between them.
Open Source Software	OSS	Software technology distributed under a license granting rights to use, inspect, modify, and redistribute its source code, subject to that license’s obligations.
Patch Cadence		The rhythm at which a supplier releases corrective and security updates for a software technology, and the corresponding rhythm at which the enterprise applies them.
Runtime		The software technology that executes code written in a given language or framework, providing the execution environment applications depend on at run time.
Software Bill of Materials	SBOM	A machine-readable record of the components, libraries, and dependencies that constitute a software technology, used to trace exposure when a vulnerability is disclosed.
Software Technologies Catalog		A consumable, self-service view built on top of a mature Software Technologies Inventory, used to discover, request, and reuse approved software technologies. Not a system of record, and not a starting point.
Software Technologies Registry		The Software Technologies Inventory expressed as a registry. The two terms name the same thing: a governed record of which software technologies exist, who owns them, and what they are permitted to do.
Software Technology		One discrete, governable software product that can be procured or obtained, installed, versioned, licensed, operated, and retired. The Noun Instance this inventory governs.
Software Technology Category		The top-level classification of a software technology by the kind of thing it is.
Software Technology Subcategory		The specific classification beneath a category, naming the particular kind of software technology.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

The Software Technologies Inventory governs every discrete, governable software product the enterprise procures, obtains, installs, operates, or depends upon. A software technology qualifies for registration when it can be obtained — purchased, licensed, or adopted as open source — installed or instantiated on infrastructure, identified by a specific version, and eventually retired when it reaches end of life. Database engines, language runtimes, compilers, middleware, message brokers, web and application servers, container platforms, operating systems, identity software, security tooling, observability tooling, and machine learning frameworks all qualify in this sense.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

The Software Technologies Inventory is equivalent to the Software Technologies Registry. The two names describe the same governed construct: the authoritative collection in which every Software Technology instance is formally registered. Registration is the act of entering a governed instance into the collection, and it is what makes the collection an authoritative system of record rather than an informal list. Instances are registered either manually, by a practitioner, or through automation that harvests and registers instances from authoritative sources. However registration occurs, a registered instance is a governed record carrying a Semantic Identifier and its governed attribute values.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Overview

Every software technology in the inventory should be classified so that it can be found, governed, and reasoned about as part of a larger set rather than in isolation. Classification is what lets an enterprise ask which technologies serve its data tier, which are approaching end of support, or which fall under a particular oversight regime. This chapter provides the value set for that classification: a representative, two-level taxonomy of categories and subcategories.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Enterprise Architecture. Enterprise Architecture cannot design a target state for a technology estate it cannot enumerate. This inventory tells Enterprise Architecture which technologies are actually in use, at which versions, and beneath which applications — the difference between a roadmap grounded in the current state and one drawn from assumption. Standards work depends on it directly: an architect cannot declare a preferred message broker or a sanctioned runtime without knowing what is already deployed and what it would cost to converge. Because Enterprise Architecture governs the Enterprise Model, this inventory is also its record of the technology layer within it.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Applications. Applications are built on, deployed on, and depend upon software technologies, so the flow runs from this inventory outward: an application record references the technologies it requires, and a technology record carries the set of applications dependent on it. This is the relationship that makes end-of-support exposure actionable — without it, knowing a database engine loses support tells the enterprise nothing about what breaks. The relationship is carried by dependency attributes on both sides and is the single most consequential link this inventory maintains.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Software Technologies is one of forty-five recognized Noun Types in the IF4IT Enterprise Inventory Management taxonomy — the master catalog of all enterprise inventory types. For the full taxonomy, the governing principles that apply across all inventories, and the Inventory of Inventories that federates them, refer to the IF4IT Enterprise Inventory Management Best Practices document.

Five Noun Types sit closest to Software Technologies. Applications are built on and run within software technologies, and software technologies are consumed by them. Vendors supply commercially licensed software technologies, and this inventory consumes vendor identity and support relationships from them. AI Agents are built on and run within machine learning and model-serving software technologies. Integrations are carried by messaging, middleware, and gateway software technologies, in a cross-referencing relationship. Data and Information assets are stored and served by database and data platform software technologies. A secondary band relates less centrally but genuinely: Capabilities, which software technologies help enable; IT Operating Environments, within which software technologies are deployed; Software Licenses and Software Subscriptions, which govern the entitlements under which technologies are used; Source Code Repositories, which hold what development software builds; Regulatory Agencies, whose requirements attach to technologies in regulated contexts; and Value Streams, for which certain technologies are critical-path dependencies. Noun Types whose inventories are not yet published are named here with their relationship; refer to the IF4IT Enterprise Inventory Management Best Practices document for their current definitions.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Section A — Sourcing and Harvesting

Before building the Software Technologies Inventory from scratch, assess whether all or part of it can be harvested from systems already operating in the enterprise. Software technologies are unusually well represented in existing systems, because deploying them leaves traces. Common sources include configuration management databases and IT service management platforms, which often already hold technology configuration items; package managers and dependency manifests, which enumerate what applications actually pull in; container registries and image scanners, which reveal what is running in containerized environments; and software discovery or asset management tooling, which detects installed software across the estate. Harvesting from these reduces the initial data entry burden, accelerates time to Crawl completeness, and surfaces technologies that manual discovery would miss — particularly the ones no one remembers deploying.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Descriptive attributes capture the identity of each software technology — what it is called, what it does, and which version the enterprise runs.

Attribute Name

Maturity

Description and Notes

UID

Crawl

Description — Machine-readable identifier generated by whatever system created or imported the record.

Benefit(s) — Allows the record to be reconciled against discovery tooling, asset platforms, and configuration data without relying on name matching.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Classification attributes capture what kind of thing each software technology is, and the properties by which the portfolio is filtered, grouped, and prioritized.

Attribute Name

Maturity

Description and Notes

Software Technology Category

Crawl

Description — The top-level classification of the technology by the kind of thing it is.

Benefit(s) — Makes the portfolio navigable and lets governance be applied by class rather than one technology at a time.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Ownership and stakeholder attributes record who is accountable for each software technology and who to reach when something about it must change.

Attribute Name

Maturity

Description and Notes

Technology Owner

Crawl

Description — The named individual accountable for the technology as a governed asset: its currency, its risk posture, and the decision to retire it.

Benefit(s) — The single highest-leverage attribute in the record. An unowned technology accumulates vulnerability and end-of-support exposure that no one is answerable for.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Lifecycle and status attributes record where each software technology sits in its life, and the dates that determine when the enterprise must act.

Attribute Name

Maturity

Description and Notes

Lifecycle State

Crawl

Description — Where the technology sits in its governed life within this enterprise.

Benefit(s) — Distinguishes what is being adopted from what is being tolerated from what is being removed, which is the basis of every portfolio decision.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Governance attributes record the decisions the enterprise has made about each software technology — whether it is approved, what standing it holds, and who decided.

Attribute Name

Maturity

Description and Notes

Approval Status

Walk

Description — Whether the technology has been through the enterprise's governance review and what that review concluded.

Benefit(s) — Distinguishes a technology that was deliberately chosen from one that simply arrived, which is the starting point for bringing an estate under control.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Strategic attributes record where each software technology is headed: whether the enterprise intends to invest in it, hold it steady, tolerate it, or remove it.

Attribute Name

Maturity

Description and Notes

Strategic Disposition

Walk

Description — The enterprise's intent for the technology over the planning horizon.

Benefit(s) — Sets the default answer to every future investment question and lets the whole portfolio be viewed as a set of intentions rather than a list of facts.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Assessment and health attributes record how the enterprise judges the current condition of each software technology, and when that judgment was last made.

Attribute Name

Maturity

Description and Notes

Currency Status

Walk

Description — How far the deployed version has drifted from the versions the supplier currently supports.

Benefit(s) — Converts version data into a conclusion that can be reported and prioritized without consulting a support matrix.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Technical attributes record what each software technology actually runs as — its deployed versions, what it runs on, what it depends on, and what it exposes.

Attribute Name

Maturity

Description and Notes

Version Deployed

[Multi-Value]

Crawl

Description — The full set of versions of this technology actually running in the enterprise.

Benefit(s) — Reveals version sprawl, which is where most unsupported exposure hides. The governed version and the deployed reality are frequently different.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Operational attributes record how each software technology is run day to day — how it is patched, how it is supported, and what is expected of it in service.

Attribute Name

Maturity

Description and Notes

Operational Status

Walk

Description — Whether the technology is currently in service, degraded, or out of service.

Benefit(s) — Separates what is deployed from what is actually working, which the lifecycle state alone does not convey.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Security attributes record what is known about each software technology’s exposure and the controls it supports, so vulnerability response can start from the record rather than from a scramble.

Attribute Name

Maturity

Description and Notes

Known Vulnerability Reference

[Multi-Value]

Walk

Description — References to catalogued vulnerabilities affecting the deployed versions of this technology.

Benefit(s) — Turns a disclosure into a query rather than a search. Joined to ownership and dependent applications, it makes response immediate rather than investigative.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Data and information attributes record what data each software technology handles, and the obligations that follow from handling it.

Attribute Name

Maturity

Description and Notes

Data Classification Handled

[Multi-Value]

Walk

Description — The highest classifications of data this technology stores, processes, or transmits.

Benefit(s) — Makes inherited obligations visible at the technology record, so deployment and patching decisions account for what the technology holds.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Geographic and jurisdictional attributes record where each software technology runs and the legal constraints that attach to running it there.

Attribute Name

Maturity

Description and Notes

Deployment Geography

[Multi-Value]

Walk

Description — The countries or regions in which the technology is deployed and operating.

Benefit(s) — Establishes which jurisdictions have a claim on the technology and the data it handles.

Source — Manual or Derived.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Temporal and effective date attributes record the dates that govern when a software technology record is valid and when it was last confirmed.

Attribute Name

Maturity

Description and Notes

Effective Date

Walk

Description — The date from which this record's content is asserted to be true.

Benefit(s) — Allows historical states to be preserved rather than overwritten, which is what makes trend and point-in-time analysis possible.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Contractual and legal attributes record the terms under which each software technology may be used, and the obligations those terms create.

Attribute Name

Maturity

Description and Notes

License Type

Crawl

Description — The specific licence governing the enterprise's use of the technology.

Benefit(s) — Determines which obligations actually attach — entitlement compliance, source disclosure, attribution, or none — and governs whether a usage change needs legal review.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Vendor and supplier attributes record who stands behind each software technology, and what the enterprise can expect from them.

Attribute Name

Maturity

Description and Notes

Supplying Vendor

Crawl

Description — The organization from which the enterprise obtains the technology, referenced by Semantic Identifier.

Benefit(s) — Connects the technology to vendor risk, support terms, and commercial relationship without restating vendor data here.

Source — Manual.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

IT environment attributes record where each software technology is deployed and what it sits on.

Attribute Name

Maturity

Description and Notes

Environments Deployed

[Multi-Value]

Walk

Description — The IT operating environments in which the technology is deployed.

Benefit(s) — Separates production exposure from lower-environment presence, so remediation is prioritized against where the technology actually matters.

Source — Derived or Manual.

Examples — Production, Staging, Test, Development

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Skills and competencies attributes record what it takes to run each software technology, and whether the enterprise has it.

Attribute Name

Maturity

Description and Notes

Required Skills

[Multi-Value]

Run

Description — The competencies needed to operate, administer, and troubleshoot the technology.

Benefit(s) — Makes the human requirement of a technology explicit, which supports hiring, training, and sourcing decisions.

Source — Manual.

Notes — Record the skills the technology genuinely demands rather than a general technology-area label.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Provenance and audit attributes record where each entry in this inventory came from, who touched it, and whether anyone has confirmed it.

Attribute Name

Maturity

Description and Notes

Record Created Date

Crawl

Description — When this inventory record was created.

Benefit(s) — Establishes the age of the entry, distinct from the age of the technology it describes.

Source — Calculated.

Notes — System-populated. Never entered manually.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Risk attributes record the exposure each software technology carries and what the enterprise intends to do about it.

Attribute Name

Maturity

Description and Notes

End of Support Risk

Walk

Description — The exposure arising from the technology running past, or approaching, the end of supplier support.

Benefit(s) — The most foreseeable risk in the portfolio and the most commonly realized. Expressing it as a judgment rather than a date makes it actionable.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Compliance and regulatory attributes record the external obligations that attach to each software technology and whether they are being met.

Attribute Name

Maturity

Description and Notes

Applicable Regulations

[Multi-Value]

Walk

Description — The external regulations or standards that attach to this technology because of what it does or what data it handles.

Benefit(s) — Establishes which technologies sit inside a regulated boundary, so oversight is applied where it is actually required.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Financial attributes record what each software technology costs the enterprise and who pays for it.

Attribute Name

Maturity

Description and Notes

Annual Recurring Cost

Walk

Description — The ongoing yearly cost of holding the technology, including licence, subscription, and support charges.

Benefit(s) — The figure that makes rationalization actionable. A duplicate technology is an observation until someone can say what removing it saves.

Source — Manual or Derived.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

Relationship attributes record the edges connecting each software technology to Noun Instances in other inventories.

Every attribute in this category is Calculated or Derived from records in other inventories. No manual data entry is required for any attribute in this category. Do not create data entry fields for any attribute listed here.

Attribute Name

Maturity

Description and Notes

Applications Dependent

[Multi-Value]

Crawl

Description — The applications built on, deployed on, or dependent upon this technology.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

The relationship between the Software Technologies Inventory and the Applications Inventory is one of consumption. Applications are built on, deployed on, and depend upon software technologies; software technologies do not depend on applications. Data flows outward from this inventory in the sense that a technology record carries the set of applications dependent on it, but the assertion originates on the application side, because an application knows which technologies it requires. Each inventory remains authoritative for its own Noun Type: the Applications Inventory governs application identity, ownership, and lifecycle, while this inventory governs technology identity, version, and support status. Neither restates the other.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

The relationship between the Software Technologies Inventory and the Vendors Inventory is one of consumption. Each commercially supplied technology originates with a vendor, and this inventory references that vendor rather than restating vendor data. The Vendors Inventory is authoritative for vendor identity, viability, risk posture, contractual relationship, and everything else that is a property of the supplier rather than of any one product it supplies. This inventory is authoritative for the technology itself. Open source technologies invert the pattern: they have no vendor, but they do have a governing community or foundation, and this inventory records that explicitly so the absence of a vendor is not mistaken for an absence of support.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

The relationship between the Software Technologies Inventory and the AI Agents Inventory is one of consumption, and it is the newest of the relationships this inventory maintains. AI agents are built on and run within the technologies governed in the Artificial Intelligence and Machine Learning Software category: machine learning frameworks, model training and serving software, vector and embedding stores, and compute acceleration software. The AI Agents Inventory is authoritative for the agents themselves — their identity, ownership, authority, autonomy, and reach. This inventory is authoritative for the technology layer beneath them. The two are governed separately because they have genuinely different lifecycles: an agent is deployed and retired as an actor in an enterprise process, while the framework it runs on is procured, versioned, patched, and supported as a technology.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

The relationship between the Software Technologies Inventory and the Integrations Inventory is a cross-reference. Neither derives from the other. Integrations are governed connections between systems, while software technologies are the products through which those connections are actually carried — message queues and streaming software, enterprise integration middleware, extract-transformation-and-load software, and application programming interface gateways. The Integrations Inventory is authoritative for the integration itself: its endpoints, its data contract, its criticality, and its owner. This inventory is authoritative for the technology carrying it. An integration record names the technologies it runs through, and a technology record carries the integrations that traverse it.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

The relationship between the Software Technologies Inventory and the Data and Information Inventory is one of consumption with inherited obligation. Database software, data warehouse software, and data platform software are the technologies through which governed data assets are stored, served, and moved. The Data and Information Inventory is authoritative for the data assets themselves — their classification, ownership, retention requirements, and regulatory status. This inventory is authoritative for the technologies managing them. What makes this relationship distinctive is that obligations flow from the data to the technology: a technology handling regulated data inherits that data’s protection, residency, and retention requirements regardless of what the technology itself is.

Software Technologies Inventory and Attributes

Thu, 23 Jul 2026 00:00:00 +0000

The Software Technologies Inventory and Attributes document is one of many Noun Type inventories in the IF4IT Enterprise Inventory Management taxonomy. Each inventory in the taxonomy governs a distinct class of enterprise asset, relationship, or organizational construct — and each contributes its records and relationships to the Enterprise Model that connects them all. The full catalog of recognized Noun Types, the principles that govern inventory design and federation, the Inventory of Inventories, and guidance for building, connecting, and maturing a complete enterprise inventory program are documented in the IF4IT Enterprise Inventory Management Best Practices document. Practitioners who find value in the Software Technologies Inventory are encouraged to explore the broader taxonomy — each additional inventory that is built and governed strengthens the Enterprise Model and expands the range of questions that AI-assisted enterprise analysis can answer. The IF4IT welcomes contributions from practitioners who develop attribute categories, attribute definitions, or governance approaches not covered in this document — your real-world experience is how this framework matures.