What Security Teams Still Get Wrong About Asset Visibility

Direct Source Verification: This story is aggregated from Forbes (forbes.com). Full reporting rights and copyright belong to the primary publisher.
Effective asset visibility requires accurate inventories, accountable ownership and processes that turn security discovery into action.

Yochai Corem is GM of Exposure Management at Check Point Software.

gettyOrganizations have more asset data than ever, but turning that data into a reliable view of what they own, operate and expose remains difficult.

A server appears in three tools with different identifiers. A cloud workload has an owner who has left the business. A forgotten website remains online after the campaign that funded it has ended. Each leaves security teams with information they still have to investigate before they can act.

Security leaders should judge asset visibility by how reliably it supports a decision. A useful inventory helps teams establish what an asset does, who is responsible for it, how it is protected and what should happen when a problem appears.

Several familiar assumptions prevent organizations from reaching that standard.

An incomplete configuration management database (CMDB) should prompt a review of how records are created, updated and retired.

Start by defining its purpose. The CMDB should record the systems, services and dependencies needed to manage business operations, with accountable owners and lifecycle status. Detailed security telemetry can remain in specialist systems, linked through reliable identifiers. An impersonating website belongs in an external threat register connected to the affected brand.

Then identify which sources can reveal missing records. Cloud platforms, endpoint management, identity providers, vulnerability scanners and procurement systems can each expose inconsistencies. Buying a service should trigger registration; retiring it should trigger checks that access, infrastructure and records have been removed.

Reconciliation should reflect the pace of change. I would set a daily reconciliation target for cloud and endpoint feeds; use deployment and retirement events to trigger updates; and review unresolved discrepancies weekly. Quarterly ownership reviews can supplement those checks.

An asset without an owner needs an interim accountable team and an escalation deadline. “Unknown” should describe an investigation in progress.

The modern attack surface spans internal infrastructure, cloud workloads, software as a service (SaaS), internet-facing systems, supplier connections and the organization’s broader digital presence.

Those categories need different forms of accountability. Infrastructure teams may manage servers, cloud teams manage workloads and business application owners sponsor SaaS services. Marketing or regional teams may control domains and social accounts. Supplier relationships require a business sponsor alongside technical oversight.

Security should establish a review and response process across those boundaries. A newly discovered domain needs ownership verification and an assessment of what it hosts. An unfamiliar SaaS service needs checks on its users, data and access. A fraudulent social account needs investigation and a disruption process.

Review frequency should follow exposure and change, with continuous discovery where practical and scheduled reviews for ownership, supplier access and dormant services. This broader scope aligns with the National Institute of Standards and Technology’s (NIST) inclusion of hardware, software, services and supplier services in asset management.

Leaders can test this assumption by following a newly discovered asset through the security process.

Does discovery trigger checks for required endpoint protection, vulnerability scanning and an accountable owner? Does an unmanaged internet-facing system reach someone authorized to restrict or remove it? Can the organization confirm that the resulting action occurred?

These outcomes show whether visibility operates as a security control. The Center for Internet Security’s (CIS) Control 1 connects inventory management with identifying and addressing unauthorized or unmanaged assets.

Useful measures include the time taken to assign ownership, the proportion of applicable assets covered by required controls and the age of unresolved discrepancies. A growing inventory count provides little reassurance when newly discovered systems remain unmanaged.

Additional tools introduce additional records, each with its own identifiers, timestamps and assumptions.

Effective reconciliation requires explicit rules. Stable cloud resource identifiers or device identifiers should take precedence over an Internet Protocol (IP) address that may change or be reused. Records need source and freshness information so teams can distinguish a current observation from a stale entry.

Organizations also need rules for conflicting fields. The identity system may establish who uses a device, while a service registry identifies the team accountable for the application it supports. Those relationships should remain distinguishable.

Cyber asset attack surface management (CAASM) can support this work. Organizations can also improve CMDB integrations, use cloud asset inventories and service catalogs, or build reconciliation workflows in their existing data platforms. The operational requirements remain consistent: reliable matching, clear authority for each field and a process for resolving exceptions.

Discovery should initiate a decision about management, protection or retirement.

A forgotten website needs an owner to confirm whether it still serves a business purpose. A vulnerable application needs assessment of its exposure, dependencies and operational constraints before a response is selected.

That decision should remain traceable through completion. If a service is retired, verify that it is no longer reachable. If a security control is applied, confirm that it covers the intended asset. Updating the inventory should accompany the operational change.

This ongoing connection between asset information and action also underpins continuous threat exposure management (CTEM).

CTEM depends on this discipline throughout scoping, discovery, prioritization, validation and mobilization.

An unknown asset cannot enter the prioritization process. A known asset without business context is difficult to rank. Missing dependencies weaken assessments of attack paths and change impact. An unknown owner delays action, while stale records undermine confirmation that an exposure has been reduced.

CAASM and external attack surface management (EASM) can support these stages by reconciling internal records and discovering internet-facing assets. Their value depends on the ownership, decision rules and response processes surrounding them.

Security leaders should expect asset visibility to connect discovery with accountable action. Every significant asset needs enough current context for someone to determine its protection requirements, address its exposures and verify the result. That is how a reliable inventory helps reduce the opportunities available to an attacker.​

Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?

Original Source
https://www.forbes.com/councils/forbestechcouncil/2026/11/20/what-security-teams-still-get-wrong-about-asset-visibility/
Visit Forbes ↗
SHARE STORY:
𝕏 f in

Related Coverage in Crime