A practical field guide for SOC analysts, security engineers, vulnerability managers, penetration testers, and cybersecurity consultants
Introduction
Discovering an exposed service is easy. Understanding whether it represents a security risk, determining who owns it, prioritizing the exposure, and ensuring that it gets fixed are the real challenges.
Attack Surface Management (ASM) is most effective when it becomes part of an organization's regular security operations rather than something performed only during an annual security assessment.
In this tutorial, we will take a practical approach to using the Attack Surface Management (ASM) and External Attack Surface Management (EASM) capabilities in Cyber Threat Analyzer (CTA).
Instead of simply listing features, we will walk through how a security professional can use CTA to:
Build an external asset inventory.
Establish an authorized assessment scope.
Discover additional subdomains.
Identify exposed network services.
Investigate TLS and HTTP configuration.
Interpret exposure findings and risk scores.
Correlate observed software with known vulnerabilities.
Prioritize remediation.
Verify whether a security improvement actually worked.
Use discovery history to monitor changes over time.
The examples use a fictional organization, example.gov.ph. Only assess domains, IP addresses, and infrastructure that you own or have explicit permission to test.
1. Start with a good assessment strategy
One mistake security teams make is attempting to scan everything immediately.
A better approach is to begin with a clearly defined scope.
Imagine that you are responsible for the external security posture of a government organization. You know about its primary website, but you are not sure whether it has additional public-facing services.
Start by preparing an initial asset list.
| Asset | Expected purpose | Assessment priority |
|---|---|---|
www.example.gov.ph | Public website | High |
mail.example.gov.ph | Email infrastructure | High |
vpn.example.gov.ph | Remote access | High |
portal.example.gov.ph | Public application | High |
old.example.gov.ph | Possibly retired service | Investigate |
Tip: Begin with business-critical assets
Do not start by treating every domain equally.
Prioritize assets that:
Process sensitive information.
Provide remote access.
Support authentication.
Handle financial transactions.
Expose administrative functionality.
Are essential to business operations.
This makes the first assessment more manageable and gives the security team a meaningful starting point.
CTA technique: Use the Authorized Scopes and Assets sections to organize what is included in your assessment.
2. Add scopes before running EASM discovery
A scope defines the boundary within which CTA performs external discovery.
Navigate to:
SECURITY MANAGEMENT → Attack Surface / EASM
Use Add Scope to register the domain or IP range you are authorized to assess.
For example:
example.gov.ph
You can define additional scopes for other domains or approved address ranges.
Tip: Separate organizational scopes
If you are managing multiple departments or customers, keep their authorized scopes clearly separated.
For example:
Municipality A:
municipality-a.gov.phMunicipality B:
municipality-b.gov.phCompany C:
company-c.com
This makes the results easier to investigate and helps prevent confusion about asset ownership.
Tip: Document the authorization
Before active assessment, record:
Who owns the asset.
Who approved the assessment.
What activities are permitted.
Which infrastructure is excluded.
When the authorization expires.
Remember: discovering a domain does not automatically mean that you have permission to scan it.
3. Register assets strategically
After establishing the scope, register the assets that you want to assess.
Select Register Asset.
Examples:
| Asset name | Target | Type |
|---|---|---|
| Main Website | www.example.gov.ph | Domain |
| Mail Gateway | mail.example.gov.ph | Domain |
| Remote Access | vpn.example.gov.ph | Domain |
| Public Portal | portal.example.gov.ph | Domain |
CTA maintains an asset inventory containing information such as authorization status, risk score, and last scan time.
Tip: Use meaningful asset names
Avoid names such as:
Server 1
Target 2
Test Host
Instead, use descriptive names:
Public Website
Government Mail Gateway
Citizen Services Portal
Remote Access Gateway
This becomes especially useful when managing dozens or hundreds of assets.
Tip: Do not confuse asset ownership with DNS relationships
A hostname may point to a third-party hosting provider or CDN.
Before assessing it, determine whether the service is within your organization's authorized scope. Do not assume that every IP address returned by DNS belongs to the organization.
4. Run your first ASM scan
Once an asset has been registered and authorized, select it from the Assets section.
Click Scan Selected.
CTA performs an outside-in assessment from the CTA server.
The current assessment checks 19 common TCP ports covering services such as:
HTTP and HTTPS
SSH
SMTP
DNS
SMB
RDP
VNC
MSSQL
MySQL
PostgreSQL
Redis
MongoDB
For reachable services, CTA records information including the port, service name, response latency, and available banner information.
For web services, it can collect:
HTTP status.
Server header.
Page title.
Security-header presence.
For TLS services, it can collect:
TLS protocol.
Cipher information.
Certificate subject.
Certificate issuer.
Subject Alternative Names.
Certificate expiry.
Tip: Pay attention to unexpected services
An exposed service is not automatically a vulnerability.
For example, an organization's VPN gateway is expected to be reachable externally. A database listening on a public IP address, however, deserves closer investigation.
Ask:
Is this service supposed to be accessible from the internet?
Is it necessary for business operations?
Is access restricted appropriately?
Is authentication required?
Is the service maintained and patched?
Is the service monitored?
Tip: Use service exposure as an investigation starting point
Suppose CTA identifies an externally reachable RDP service.
Do not immediately conclude that the server is compromised.
Instead, investigate:
Whether public RDP access is intentional.
Whether access is restricted through VPN or allowlisting.
Whether MFA is enforced.
Whether the system is patched.
Whether authentication failures appear in security logs.
The purpose of ASM is to identify what deserves attention.
5. Learn to interpret the risk score
CTA uses a transparent, rule-based risk-scoring model.
The current findings and their contributions include:
| Finding | Severity | Risk contribution |
|---|---|---|
| Sensitive service reachable | Medium | +15 |
| Legacy TLS protocol | Medium | +15 |
| Expired TLS certificate | High | +25 |
| TLS hostname mismatch | High | +25 |
| Plaintext HTTP exposed | Low | +8 |
The asset risk score is capped at 100.
The resulting risk levels are:
| Score | Risk level |
|---|---|
| 80–100 | Critical |
| 50–79 | High |
| 25–49 | Medium |
| 1–24 | Low |
| 0 | No scored finding |
Practical example
Suppose a public-facing asset has:
SSH exposed: +15
RDP exposed: +15
Expired TLS certificate: +25
Plaintext HTTP: +8
Its resulting score is:
[
15+15+25+8=63
]
<badge color="warning">High risk</badge>
The asset has a score of 63.
This gives the analyst a clear starting point for investigation.
Tip: Never rely on the score alone
A risk score is a prioritization aid, not a substitute for security judgment.
For example, a publicly exposed administrative service may deserve immediate attention even if the total score is relatively low.
Consider:
Business criticality.
Internet accessibility.
Sensitivity of the data.
Authentication controls.
Known exploitation.
Existing compensating controls.
The question is not simply, "Which asset has the highest score?"
The more useful question is:
Which exposure creates the greatest realistic risk to the organization?
6. Use EASM discovery to find what you might have missed
A manually maintained asset inventory is rarely complete.
Organizations create new subdomains, deploy new applications, migrate infrastructure, and sometimes forget to retire old services.
This is where CTA's EASM discovery becomes useful.
Select Run EASM Discovery.
The discovery workflow uses:
Certificate Transparency lookup through crt.sh.
A bounded common-subdomain discovery process.
DNS resolution.
Assessment of assets that are authorized for probing.
Software fingerprinting based on observed information.
CVE correlation.
Practical example
You initially registered:
example.gov.ph
During discovery, CTA identifies:
www.example.gov.phmail.example.gov.phportal.example.gov.pholdportal.example.gov.ph
The most interesting discovery may not be the main website.
It may be the old portal.
Why?
Because older applications are sometimes overlooked during infrastructure upgrades. They may have outdated software, forgotten administrative accounts, or unnecessary services.
Tip: Investigate unfamiliar subdomains first
When EASM identifies a new hostname:
Determine whether it belongs to your organization.
Identify its business owner.
Determine whether it is still active.
Check whether it is included in the authorized scope.
Review its exposed services.
Decide whether it should remain online, be secured, or be retired.
Do not automatically treat every discovered hostname as an authorized scanning target.
Tip: Watch for changes, not just new discoveries
A previously known hostname that suddenly resolves to a different IP address can be just as interesting as a newly discovered hostname.
Changes in infrastructure may indicate:
Hosting migration.
DNS configuration changes.
Deployment of a new service.
Infrastructure replacement.
Unexpected configuration changes.
Investigate changes in context rather than assuming that every change represents malicious activity.
7. Correlate exposed software with vulnerability intelligence
One of the most useful ways to improve an ASM workflow is to connect externally observed technology with vulnerability information.
CTA integrates its external exposure information with its vulnerability intelligence capabilities.
These include:
National Vulnerability Database (NVD).
CISA Known Exploited Vulnerabilities (KEV).
FIRST Exploit Prediction Scoring System (EPSS).
Practical example
Suppose an external web server exposes a software banner that indicates a potentially outdated software component.
CTA can use the observed vendor, product, and version information to look for applicable vulnerability records.
The analyst should then examine:
Whether the software identification is reliable.
Whether the affected version matches.
Whether the CVE applies to the actual configuration.
Whether the vulnerability appears in CISA KEV.
Whether the EPSS score indicates meaningful exploitation probability.
Whether the affected service is internet-facing.
Tip: Prioritize KEV-listed vulnerabilities
A vulnerability listed in CISA KEV has additional significance because it is known to have been exploited in the wild.
When a potentially affected internet-facing service also has a KEV-listed vulnerability, investigate it promptly.
EPSS provides another prioritization signal, but it is not proof that an attack is occurring.
Tip: Treat software fingerprints as evidence, not certainty
Server banners can be misleading.
Software versions may be hidden, modified, or backported by vendors.
Always verify the actual software version and patch status before declaring a vulnerability confirmed.
8. Connect external exposure with endpoint security context
External attack surface visibility becomes more useful when combined with endpoint telemetry.
CTA supports linking an external asset with an enrolled CTA endpoint through its API.
This allows external asset information to be considered alongside recent alerts and events associated with that endpoint.
Consider this example:
EASM identifies a public-facing server.
The asset is linked to an enrolled endpoint.
CTA identifies suspicious process activity associated with that endpoint.
The analyst investigates whether the activity is related to the externally exposed service.
The investigation combines external exposure evidence with endpoint activity.
This creates a more useful security investigation than looking at the network exposure or endpoint alerts separately.
Tip: Correlation is not proof of compromise
An external exposure and a suspicious endpoint event occurring on the same machine do not automatically establish that the exposure caused the activity.
Look for supporting evidence:
Relevant timestamps.
Process execution history.
Authentication records.
Network connections.
File changes.
Related alerts.
Use the combined evidence to guide investigation.
9. Make rescan verification part of your remediation process
One of the most overlooked activities in vulnerability management is verifying that a fix actually worked.
Finding a problem is only the beginning.
Suppose CTA identifies:
Publicly reachable RDP.
An expired certificate.
A weak TLS configuration.
The infrastructure team implements changes.
What happens next?
Do not simply close the finding because someone reported that the issue was fixed.
Run another assessment.
Recommended remediation workflow
Record the original finding.
Assign the remediation task to the responsible team.
Document the corrective action.
Perform the infrastructure change.
Run Scan Selected again.
Compare the new results with the previous assessment.
Confirm whether the exposure has disappeared or changed.
Retain the evidence of the verification.
Tip: Use the fix-and-rescan method
This creates a repeatable verification loop:
Discover → Assess → Prioritize → Remediate → Rescan → Verify
For security consultants, this also provides a practical way to demonstrate whether agreed corrective actions have changed the externally observable security posture.
10. Use EASM history to establish a monitoring routine
A single assessment gives you a snapshot.
Repeated assessments provide visibility into changes.
CTA's EASM discovery runs retain information such as:
Discovered asset counts.
Scanned asset counts.
Vulnerability correlations.
Observed software.
Attack-surface changes.
Unified-risk history.
The default EASM background interval is 24 hours. It can be configured using:
CTA_EASM_INTERVAL_SECONDS
The minimum configured interval is 300 seconds.
Recommended monitoring routine
| Frequency | Activity |
|---|---|
| Daily | Review new discovery runs and unexpected asset changes |
| Weekly | Review high-risk assets and unresolved findings |
| Monthly | Review asset ownership and authorization |
| After remediation | Rescan affected assets |
| After infrastructure changes | Reassess relevant external services |
Tip: Investigate assets that disappear
If an asset disappears from discovery, do not immediately assume that it was decommissioned.
Check whether:
DNS records changed.
The hosting provider changed.
The service was intentionally removed.
The domain temporarily stopped resolving.
The discovery provider returned incomplete information.
Disappearance from discovery is not necessarily proof that an asset no longer exists.
11. Tips for MSSPs and security consultants
ASM/EASM can also support recurring security assessment services.
For an MSSP or security consultant, a useful approach is to maintain a separate authorized scope for each customer.
A practical customer engagement can follow this sequence:
Before assessment
Obtain written authorization.
Define the customer's domains and IP ranges.
Document exclusions.
Establish the assessment window.
During assessment
Register the approved assets.
Perform external scans.
Run EASM discovery.
Review exposed services.
Investigate vulnerability correlations.
After assessment
Prioritize findings.
Prepare a report.
Assign remediation responsibilities.
Rescan after corrective action.
Document unresolved exposures.
CTA's tenant-aware ASM architecture and API provide a foundation for managing customer-specific assessment information.
However, an MSSP should still validate tenant permissions, authorization workflows, and report separation before offering the capability as a production service.
Tip: Give customers evidence, not just scores
A good external attack surface report should include:
Asset name and target.
Authorization status.
Assessment timestamp.
Observed services.
Finding description.
Severity and risk contribution.
Supporting technical evidence.
Recommended remediation.
Verification status.
A customer needs to understand why a finding matters and what to do about it.
12. Useful API operations for automation
CTA exposes ASM and EASM functionality through REST API routes.
Some useful operations include:
| Operation | Endpoint |
|---|---|
| List provider definitions | GET /api/v1/asm/providers |
| Create provider connection | POST /api/v1/asm/providers/connections |
| Test provider connection | POST /api/v1/asm/providers/connections/{connection_id}/test |
| Request scope verification | POST /api/v1/asm/scopes/{scope_id}/verification |
| Verify scope | POST /api/v1/asm/scopes/{scope_id}/verify |
| Run EASM discovery | POST /api/v1/easm/discover |
The API can be useful when integrating external exposure information with reporting, ticketing, and other security operations.
Use the API documentation and the authorization requirements of your installed CTA version when building integrations.
13. Important limitations every analyst should understand
Effective security work requires knowing what a tool does not do.
CTA's current ASM/EASM assessment has several boundaries:
The active scan covers 19 common TCP ports, not every possible port.
It does not sweep entire subnets to discover arbitrary unknown hosts.
Its scans provide an outside-in view from the CTA server.
Host firewalls and network restrictions can affect what is visible.
It does not yet use agent-collected listening-socket or firewall-rule information as an inside-out inventory.
Its external discovery uses Certificate Transparency and bounded common-subdomain discovery; it should not be confused with unrestricted internet-wide discovery.
It does not perform intrusive vulnerability testing or exploit vulnerabilities.
Observed technology fingerprints and CVE matches require validation.
Provider integrations and continuous monitoring should be tested in the actual deployment environment.
For deeper assessments, combine ASM with authenticated vulnerability scanning, endpoint telemetry, configuration reviews, and authorized penetration testing.
14. A practical checklist for your first week with CTA ASM/EASM
Here is a simple operational plan for a security team adopting CTA.
Day 1 – Establish the scope
Identify authorized domains and IP addresses.
Obtain written assessment permission.
Register scopes.
Document exclusions.
Day 2 – Build the inventory
Register important external assets.
Review asset ownership.
Confirm authorization status.
Identify critical business services.
Day 3 – Perform the initial assessment
Scan approved assets.
Review the Services section.
Examine ASM Findings.
Investigate exposed administrative services.
Review TLS and HTTP configuration.
Day 4 – Discover additional assets
Run EASM discovery.
Review newly discovered hostnames.
Verify ownership.
Investigate unfamiliar assets.
Review EASM Runs.
Day 5 – Prioritize and remediate
Review high-risk findings.
Investigate CVE correlations.
Check KEV and EPSS information.
Assign corrective actions.
Plan verification scans.
Following weeks – Establish continuous monitoring
Review scheduled discovery results.
Investigate changes.
Rescan after remediation.
Maintain accurate asset ownership and authorization records.
Conclusion: Make Attack Surface Management an Operational Discipline
ASM should not be treated as another scanner that produces a list of open ports.
Its real value comes from repeatedly asking the right questions:
What assets are exposed?
Are they authorized?
Which services are reachable?
Are those services necessary?
Is the software potentially vulnerable?
Which exposures deserve immediate attention?
Has the remediation actually worked?
CTA's ASM/EASM capabilities bring external asset discovery, service assessment, exposure findings, and vulnerability intelligence into the same cybersecurity platform.
For SOC analysts, this creates additional context for investigations.
For security engineers, it provides a repeatable way to identify and verify external configuration problems.
For vulnerability managers, it helps connect exposed services with known vulnerability intelligence.
For MSSPs and security consultants, it provides a foundation for recurring, evidence-based external exposure assessments.
The goal is not simply to discover your attack surface. The goal is to understand it, manage it, and continuously reduce unnecessary exposure.
No comments:
Post a Comment