Tuesday, October 27, 2026

Seeing Your Network the Way an Attacker Does: Attack Surface Management in CTA

 Most teams only learn what they expose to the network when someone else finds it first. CTA's Attack Surface / EASM tab gives SOC analysts and security engineers that view first: which hosts and domains are reachable, which services answer, what the certificates and web servers say about them, and how risky each exposure is, all in one place next to your alerts and vulnerability data.

Why attack surface visibility matters

Endpoint detection tells you what happened on a machine. It does not tell you that a forgotten RDP port, a database listening on the LAN, or an expired certificate gave an attacker a way in. Attack surface management (ASM) closes that gap by inventorying what is reachable and treating every exposed service as a finding to be triaged.

In CTA the tab sits under SECURITY MANAGEMENT in the sidebar, beside Vulnerability Management, Endpoint / Fleet Management, Deploy Agents and Agent Updates. It combines two engines:

  • ASM: scans assets you have registered and records evidence of what is exposed.
  • EASM: continuously discovers more of your external footprint inside the scopes you authorized, and feeds what it learns into vulnerability management.

Built to be safe to run: authorization first

The tab only touches what you have explicitly registered under your tenant, and the checks are deliberately light. Discovery uses DNS resolution, bounded TCP connects, TLS certificate inspection and small HTTP metadata requests.

It does not exploit anything, attack credentials, brute-force subdomain names or run arbitrary commands. The Certificate Transparency lookup and the small common-subdomain set are bounded and conservative by design.

That makes it something a security team can run against production without a change-control fight, and something an MSSP can show a client as evidence of what was and was not done. Findings describe observed exposure. They are not claims that a service is exploitable or that a host is compromised.

How analysts use it

The workflow is five steps, and the buttons across the top of the tab map onto them. Everything is filtered to the logged-in user's tenant.

  1. Add Scope (administrator). Enter a domain or IP you are authorized to assess, for example your company domain. Scopes are the authorization boundary for EASM discovery.
  2. Register Asset (administrator). Give a name, a target (domain, IP or hostname) and a type. The asset is saved as authorized and appears in the Assets sub-tab.
  3. Scan Selected (operator or above). Select an asset row and scan it. CTA resolves the target, checks a set of common ports, and collects TLS and HTTP metadata. It then stores the services and findings and updates the asset's risk score and last-scan time.
  4. Run EASM Discovery (operator or above). One continuous-EASM cycle for your tenant: Certificate Transparency lookups for in-scope domains, bounded DNS discovery, probing of what it finds, software fingerprinting from observed banners, and CVE correlation.
  5. Review the sub-tabs. Work through the results, then rescan after a fix to confirm the exposure is gone.

The sub-tabs are the working surface:

Sub-tab

What it shows

Typical use

Assets

Registered targets with authorization, status, risk score and last scan

Pick what to scan, sort by risk

Authorized Scopes

The domains and IPs approved for assessment

Audit what is in bounds

ASM Findings

Observed exposures by severity

Triage queue

Services

Ports and services seen per asset and IP

Confirm what is listening

EASM Runs

History of discovery cycles with counts of assets discovered, scanned and vulnerabilities correlated

Check the scheduler is running

Discovery also runs on its own. The default background interval is 24 hours and can be changed with the CTA_EASM_INTERVAL_SECONDS setting (minimum 300 seconds).

What it finds, and how risk is scored

Each scan checks 19 common ports, covering web, SSH, SMTP, DNS, mail, SMB, RDP, VNC and the usual database and data-store ports. For every open service it records the port, service name, latency and banner. For web ports it adds the HTTP status, server header, page title and which security headers are present. For TLS ports it adds the protocol, cipher, certificate subject, issuer, SAN list and expiry.

Findings come from a small, readable rule set, and each adds to the asset's risk score (capped at 100):

Finding

Severity

Risk added

Triggered by

Sensitive service reachable

Medium

15

SSH, SMB, RDP, MSSQL, MySQL, PostgreSQL, Redis or MongoDB answering on a scanned port

Legacy TLS protocol

Medium

15

TLS 1.0 or 1.1 on a TLS port

TLS certificate expired

High

25

Certificate past its expiry date

TLS hostname mismatch

High

25

Certificate does not match the target name

Plaintext HTTP exposed

Low

8

An HTTP service responding on port 80, 8080 or 8081

The asset's score maps to a level: 80 and above is critical, 50 and above is high, 25 and above is medium, anything above 0 is low. Because the rules are simple, an analyst can always see why an asset scored what it did. An asset with two sensitive ports open scores 30, for example, and the Findings sub-tab shows which two.

From a port list to a risk chain

The part that sets CTA apart from a standalone scanner is what happens after discovery. EASM connects the exposure it sees to the rest of the platform:

Internet-facing asset → exposed service → detected software → CVE → CISA KEV / EPSS → linked endpoint → suspicious activity → unified risk

  • Software to CVE. Software seen in HTTP and server banners is turned into the same software-to-CVE correlation used by Vulnerability Management. A CVE is correlated only when the observed vendor, product and version match an NVD CPE configuration with enough evidence, so you get fewer speculative matches.
  • Prioritization. Matches are enriched with the CISA Known Exploited Vulnerabilities catalog and EPSS scores, so a KEV-listed flaw on an exposed service rises above a theoretical one.
  • Endpoint correlation. An external asset can be linked to an enrolled CTA endpoint through the API. CTA then checks recent alerts and events for that endpoint and adds an evidence-backed activity contribution to the risk chain. This is correlation, not proof of compromise.
  • History. EASM runs, observed software, surface changes and unified-risk history are retained, so you can see what appeared, changed or disappeared between cycles.

The same data is available over the API under /api/v1/asm/* and /api/v1/easm/*, so findings can feed ticketing, reporting or other automation.

Why use it: the advantages

  • One console, not three tools. Exposure, vulnerabilities and endpoint alerts live in the same product, so an analyst does not copy IPs between a scanner, a CVE tracker and the SIEM.
  • Evidence you can defend. Every finding is an observation with the port, service and certificate details behind it. Nothing is guessed, and CVEs are matched only on sufficient version evidence.
  • Authorization built in. Only registered, authorized assets are scanned, and probing is low impact. That suits regulated environments and client work.
  • Multi-tenant from the ground up. Every ASM table carries a tenant ID and every route needs an explicit tenant context. An MSSP can run many clients from one deployment and follow its existing tenant delegation model, with no separate ASM permission system to manage.
  • Continuous, not a yearly audit. Scheduled discovery and retained history show change over time. A new service appearing overnight is visible the next morning.
  • Prioritized by what attackers actually use. KEV and EPSS enrichment, plus the link to endpoint activity, push the exposures that matter to the top.
  • Open and automatable. A documented REST API lets you pull findings into reports or workflows, and the scoring rules are simple enough to explain to a client or auditor.

In practice that gives three groups different wins. SOC analysts get a triage queue with context. Security engineers get a verification loop: fix, rescan, confirm. MSSPs get per-client exposure data, kept separate by tenant, that they can pull through the API.

Limitations to plan around

This is a foundation, not a full commercial ASM replacement, and it is worth knowing where its edges are:

  • Registered assets only. It does not sweep a subnet to find unknown hosts. EASM discovery finds subdomains of the domain scopes you add, but it cannot find unregistered internal machines.
  • A fixed port list. Scans cover 19 common ports. Services on other ports, such as WinRM or LDAP, are not seen.
  • An outside-in view. Scans run from the CTA server, so results show what that server can reach, not everything listening on the host. Host firewalls will hide ports from the scan.
  • No inside-out inventory. The tab does not yet use agent-collected data such as listening sockets or firewall rules.
  • Not yet included: passive DNS ingestion, cloud inventory, authenticated SaaS inventory, and intrusive vulnerability testing. The project documentation says these should be added only with evidence and explicit authorization controls.

Pair it with your endpoint telemetry, a full vulnerability scanner for authenticated checks, and your existing asset inventory. Use ASM as the outside-in view that tells you what to look at first.

Getting started

  • Confirm you have an administrator account for scopes and assets, and an operator account for scanning
  • Open SECURITY MANAGEMENT → Attack Surface / EASM
  • Add a scope for each domain or IP range you are authorized to assess
  • Register your first assets: a public site, the CTA server, a gateway
  • Run Scan Selected on each and read the ASM Findings and Services tabs
  • Decide which exposures are intended, and fix or restrict the rest
  • Run EASM Discovery and check EASM Runs to confirm the scheduler is working
  • Rescan after each fix to confirm the exposure is closed

No comments:

Post a Comment

Hands-On with CTA ASM/EASM: Practical Techniques, Tips and Tricks for Effective Attack Surface Management

  A practical field guide for SOC analysts, security engineers, vulnerability managers, penetration testers, and cybersecurity consultants I...