Image without description
  • Jacco Meijer
  • |
  • Aug 15, 2025

Asset security

Information asset identification and classification from a security perspective

Data security

Data security can be seen as a specialization of asset security which is what the post below is about.

Image without description
  • Jacco Meijer
  • |
  • Aug 8, 2025

Data security

Data identification, data roles and data classification from a security perspective

Information assets

Assets in this post are information systems. Systems that processes, transfer or store data. From a security perspective an asset is any system that has value. These assets can be tangible, intangible and logical.

TypeDescriptionExamples
TangiblePhysical assets that can be seen and measuredhardware, network infrastructure
IntangibleNon-physical assets that represent valuesoftware, databases, information stores
Hybrid / LogicalInformation assets that are logical or part tangible and part intangiblenetworks, information systems

Asset identification

Assets are added and removed from organizations frequently. These changes have significant impact on organization security which makes it essential to identify new assets. The more is known about the new assets, the better the assets can be protected.

Because of the importance and the complexity of managing all assets in a large organization, a broad variety of tooling is used.

Scanners, directories, license trackers, discovery services, etc. All contribute to asset identification. AI helps by handling large amounts of data and analysis.

Asset management

Because of the many tools working together, all information should be consolidated into a single source of truth managed by a single authority. This concept leads to the specific field of IT Asset Management (ITAM).

The major goals of ITAM are more broad than only the cyber security context:

  • Reduce costs by avoiding over-purchasing and under-utilization
  • Ensure compliance with software licensing and regulatory requirements
  • Improve operational efficiency and decision-making
  • Support cyber security by maintaining accurate asset inventories

ISO 19770 is a family of international standards focused on ITAM. It provides frameworks and specifications to help organizations manage their IT assets such as hardware, software, subscriptions, and cloud services effectively and in compliance with governance and licensing requirements.

Asset classification

Asset classification is assigning a value and a sensitivity level based on content and context. Asset categorization is grouping the classified assets.

It is common to value an asset in two ways. The quantitative value is the estimation of the numerical asset value and the qualitative value is the assessment of an assets importance or impact.

Classification is important because treating security risks for all assets equally is a costly approach. It is much more efficient to classify assets on sensitivity and differentiate accordingly.

Asset classification Levels

AI is very suitable for scaffolding text. This is an example AI prompt on setting up asset classification levels.

create an Asset classification levels table:
- rules:
  - use tiers where tier 0 is the most restricted
  - include mixed tier
  - include example systems and devices
  - include description
  - include requirements
  - output visual markdown table

Generated asset classification levels table

TierDescriptionExample Systems/DevicesRequirements
Tier 0Most restricted. Critical assets with highest confidentiality, integrity, and availability needs.Core banking systems, encryption key vaults, national ID databasesMulti-factor authentication, Strict access control, Real-time monitoring, Encrypted storage
Tier 1Highly sensitive. Important for business continuity and compliance.HR systems, financial reporting tools, internal legal databasesRole-based access, Regular audits, Secure backups, Patch management
Tier 2Moderately sensitive. Operational systems with limited exposure risk.CRM platforms, internal collaboration tools, inventory systemsStandard authentication, Periodic vulnerability scans, User training
Tier 3Low sensitivity. Public-facing or non-critical systems.Company website, marketing tools, public documentation portalsBasic security hygiene, Monitoring for anomalies, Regular updates
Mixed TierAssets spanning multiple tiers due to integrated functions or shared infrastructure.Hybrid cloud environments, shared databases, mobile device fleetsSegmentation controls, Tier-specific policies per component, Continuous risk assessment

How organizations classify assets

Key regulations and frameworks define how organizations classify and categorize information assets, often shaping their asset identification and protection policies.

Below an example AI prompt that generates an overview of common regulations on asset classification for jurisdictions EU, USA and China.

create a matrix:
- rows:
  - GPDR (EU)
  - NIS 2 (EU)
  - NIST SP 800-60 (USA)
  - FIPS 199 (USA)
  - FISMA (USA)
  - MLPS (China)
  - PIPL (China)
- columns:
  - classify
  - category
- cells: summarized search results in text 
- rules:
  - generate 5 variants for each term and log them
  - also search for variants
  - limit search to official regulation text
  - output markdown table that can be copied

Generated regulation sources table

RegulationSource URL
GDPR (EU)https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
NIS 2 Directive (EU)https://eur-lex.europa.eu/eli/dir/2022/2555/oj/eng
NIST SP 800-60 (USA)https://csrc.nist.gov/pubs/sp/800/60/v2/r1/final
FIPS 199 (USA)https://csrc.nist.gov/pubs/fips/199/final
FISMA (USA)https://csrc.nist.gov/topics/laws-and-regulations/laws/fisma
MLPS 2.0 (China)https://openstd.samr.gov.cn/bzgk/gb/newGbInfo?hcno=BAFB47E8874764186BDB7865E8344DAF
PIPL (China)https://en.spp.gov.cn/2021-12/29/c_948419.htm

Generated asset classification regulations matrix

FrameworkClassifyCategory
GDPR (EU)Used in guidance for security levels (e.g., EU RESTRICTED), not in the core regulation.Defines “special categories” of sensitive personal data (e.g., health, race).
NIS 2 (EU)Refers to classifying entities by criticality (essential vs. important).Entities are grouped into categories that determine obligations and oversight.
NIST SP 800-60 (USA)Implies classification through mapping data to impact levels.Central concept: categorizing data by confidentiality, integrity, and availability impact.
FIPS 199 (USA)Classification not used; focuses on categorizing systems by impact on security objectives.Defines categories based on impact levels for confidentiality, integrity, and availability.
FISMA (USA)Requires categorization of systems; relies on NIST guidance, not classification terminology.Uses security categories to guide risk management and control selection.
MLPS (CHINA)Uses formal classification levels (1–5) based on system sensitivity and national interest.Categorizes systems by role and criticality to determine protection requirements.
PIPL (CHINA)Implies classification via “sensitive personal information” requiring stricter handling.Defines categories of personal data, especially sensitive types like biometrics and health data.

Conclusion

Understanding and securing information assets is a foundational aspect of modern cyber security.

Effective asset management supported by tooling, AI, ITAM, and standards like ISO 19770 ensure that organizations maintain visibility and control over their digital landscape.

Classification and categorization of assets allow for differentiated security measures, optimizing resource allocation and risk mitigation. Regulatory frameworks across jurisdictions reinforce the importance of structured asset handling, each offering unique perspectives on how data and systems should be valued and protected.

Ultimately, mature asset management empowers organizations to safeguard their operations, comply with regulations, and respond dynamically to evolving threats.


Other posts

Image without description
  • Jacco Meijer
  • |
  • Aug 8, 2025

Data security

Data identification, data roles and data classification from a security perspective

Image without description
  • Jacco Meijer
  • |
  • Jul 25, 2025

Threat modeling, security frameworks and Enterprise Architecture

Combining ISO 27001, NIST CSF and threat modeling with Enterprise Architecture strengthens all elements

Image without description
  • Jacco Meijer
  • |
  • Jul 18, 2025

Threat modeling as part of a risk framework

Threat modeling in the context of ISO 27001 and NIST CSF

Image without description
  • Jacco Meijer
  • |
  • Jul 11, 2025

Cyber security risk frameworks

Managing cyber security risk with ISO 27001 and NIST CSF

Image without description
  • Jacco Meijer
  • |
  • Jun 27, 2025

NIST CSF Tiers for cyber security risk governance and management

NIST CSF 2.0 contains useful tiers for Capability Maturity Modeling in Enterprise Architecture

Image without description
  • Jacco Meijer
  • |
  • Jun 20, 2025

Archimate risk assessment elements

A few simple specializations for working with risk assessments in Archimate

Image without description
  • Jacco Meijer
  • |
  • Jun 13, 2025

Security principles in Enterprise Architecture

Adding security principles to Enterprise Architecture for NIST CSF and ISO 27001

Image without description
  • Jacco Meijer
  • |
  • Jun 6, 2025

Combining ISO 27001 and NIST CSF

How to use ISO 27001 and NIST Cyber Security Framework together

Image without description
  • Jacco Meijer
  • |
  • May 1, 2025

CISSP certification and Enterprise Architecture

How do the CISSP certification domains relate to Enterprise Architecture and the ArchiMate layers?

Image without description
  • Jacco Meijer
  • |
  • Apr 23, 2025

Architect roles in the ArchiMate context

An ArchiMate model that maps architect roles to the ArchiMate framework layers.

Image without description
  • Jacco Meijer
  • |
  • Mar 18, 2025

Visualizing IT Architecture in three languages, UML, C4 and ArchiMate

What are the differences and what are these languages most used for?

Image without description
  • Jacco Meijer
  • |
  • Feb 18, 2025

OAuth 2.0 and OpenID Connect Sequence Diagrams

Technical specs can be hard to read. While still highly technical, the UML Sequence Diagrams provided in this blog are a lot easier to understand.

Image without description
  • Jacco Meijer
  • |
  • Jan 9, 2025

OWASP and CISSP

OWASP recommendations from the independent information security certification CISSP.

Image without description
  • Jacco Meijer
  • |
  • Mar 21, 2024

UI Library with MDX documentation

Using the simple Render JSX plugin for Esbuild this post shows how to setup a simple UI library.

Image without description
  • Jacco Meijer
  • |
  • Mar 20, 2024

Render JSX plugin for Esbuild

Transform Esbuild generated JSX bundles to HTML pages.

Image without description
  • Jacco Meijer
  • |
  • Mar 19, 2024

Esbuild as a static site generator for MDX

Static site generators gain popularity. This blog is about using Esbuild as a static site generator for MDX.

Image without description
  • Jacco Meijer
  • |
  • Mar 18, 2024

11ty and Github pages

Simplifying the Contentful-Gatsby-Netlfy trio.

Image without description
  • Jacco Meijer
  • |
  • Jun 30, 2022

NPM7 and @npmcli/arborist

@npmcli/arborist is a powerful library that handles the new NPM 7 workspaces. This blog is about a simple make tool that uses the library.

Image without description
  • Jacco Meijer
  • |
  • May 12, 2022

Comparing React app, Nextjs and Gatsby

A new React project starts with a React toolchain. Main tools in the chains are SSR, React server components and GraphQL.

Image without description
  • Jacco Meijer
  • |
  • May 10, 2022

Versioning strategy for NPM modules

It is important to be able to bump the version of a NPM package without side effects.

Image without description
  • Jacco Meijer
  • |
  • Apr 12, 2022

React component themes and CSS variables

Creating React components with flexible themes by using CSS variables.

Image without description
  • Jacco Meijer
  • |
  • Mar 21, 2022

Content modeling with variants

The efficiency of a variant field in a content model.

Image without description
  • Jacco Meijer
  • |
  • Mar 12, 2022

Documentation

Documenting a software project is challenging. Here's a few simple guidelines that help a team writing clear documentation.

Image without description
  • Jacco Meijer
  • |
  • Mar 11, 2022

Javascript history

In 1986 David Ungar and Randall B. Smith developed Self at Xerox PARC. Inspired by Java, Scheme and Self Brendan Eich created Javascript in 1995.

Image without description
  • Jacco Meijer
  • |
  • Mar 10, 2022

On Javascript transpilers, bundlers and modules

There's Javascript transpilers, modules, bundles and bundlers. This is a brief overview of all of these.

Image without description
  • Jacco Meijer
  • |
  • Feb 11, 2022

Agile Scrum

The Agile Scrum framework is flexible enough to be used in many different ways. Here's one way of working.

Image without description
  • Jacco Meijer
  • |
  • Jan 20, 2022

What happened to Wheelroom?

Founded in 2018. Started to fly in 2020 and abandoned in 2021. What happened?

Image without description
  • Jacco Meijer
  • |
  • Jan 19, 2022

Contentful, Netlify and Gatsby four years later

What did we learn from using Contentful for four years?

Image without description
  • Jacco Meijer
  • |
  • Jan 18, 2022

Typescript interface for React UI components

How to define an interface for React UI components that prevents breaking changes.

Image without description
  • Jacco Meijer
  • |
  • Jan 17, 2022

Naming React components

What's in a name? A clear naming strategy helps developers communicate. Most devs rather spend time writing component code than wasting time on a good component name.