OT Attack Surface Assessment: How to Find Internet Exposed ICS
An industrial system does not need to be compromised to become a security concern.
If a PLC, HMI, remote access gateway, engineering system or industrial service is unexpectedly visible from the public Internet, the organization has already gained an important piece of information about its attack surface.
The difficult part is knowing what is actually exposed.
Industrial organizations may have public IP addresses, cloud services, vendor connections, remote access infrastructure, forgotten systems and temporary services that are not always reflected accurately in internal documentation.
An external attack surface assessment provides a controlled way to discover what an organization appears to expose to the Internet, validate whether the exposure belongs to the organization and determine which findings require attention.
What Is an OT External Attack Surface?
An OT external attack surface is the collection of industrial systems, services, network endpoints and supporting infrastructure that can be reached or identified from outside the organization’s trusted network.
This can include systems directly connected to the Internet as well as remote access infrastructure and other externally visible services that provide a path toward OT environments.
The important distinction is between visibility and vulnerability.
An asset being visible from the Internet does not automatically mean that it is vulnerable. It does mean that the organization should understand why it is visible, whether that exposure is intentional and whether the security controls are appropriate.
Why Internet Exposure Matters in OT
CISA states that Internet accessible assets can include IIoT devices, SCADA systems, ICS and remote access technologies, and warns that unsecured exposure increases operational and security risk.
Industrial systems can also be discovered through Internet search and discovery platforms. This means an organization does not necessarily need to know that a particular system is exposed before another party can discover evidence of it.
The first objective of an external assessment is therefore simple:
Know what the Internet can see before someone else tells you.
External Exposure Is Not the Same as Internet Compromise
This distinction is essential when reporting an external attack surface assessment.
An external assessment may identify an open service, a device banner, a certificate, a hostname or other publicly observable information.
That evidence does not automatically prove that the system has been compromised.
It may indicate exposure, misconfiguration, information disclosure or a potential attack path that requires further investigation.
A professional report should clearly separate what was observed from what has been inferred.
What Can an External OT Assessment Discover?
Depending on the authorized scope and available information, an external assessment can examine:
- Public IP addresses
- Internet exposed services
- DNS records
- Subdomains
- TLS certificates
- Remote access gateways
- Web interfaces
- VPN infrastructure
- Industrial service indicators
- Cloud connected services
- Unexpected network exposure
- Historical exposure
The exact visibility depends on the organization’s infrastructure and the data available to the external assessment.
Start With the Organization’s Known Internet Footprint
An external assessment should begin with information that the organization already knows.
- Official domains
- Known public IP ranges
- Autonomous System Numbers
- Cloud environments
- Remote access domains
- Public VPN endpoints
- Vendor managed services
This creates a baseline for external discovery.
The assessment can then compare the organization’s known footprint with what public sources actually reveal.
Use OSINT to Expand the Asset Picture
Open source intelligence can reveal relationships between domains, IP addresses, certificates, organizations and publicly visible services.
Useful sources can include:
- DNS records
- Certificate transparency information
- WHOIS and registration information where available
- ASN information
- Public search engines
- Internet scanning indexes
- Organization owned documentation
- Public technical information
OSINT is particularly useful because it can identify assets that are not obvious from the organization’s main website or published documentation.
How Shodan Fits Into an OT Attack Surface Assessment
Shodan is an Internet search platform that indexes information about Internet connected devices and services.
CISA specifically identifies Shodan and similar platforms as tools that organizations can use to identify Internet exposed assets, including IoT, IIoT and industrial control systems.
Shodan can return information such as IP addresses, ports, service banners and other metadata. It also uses tags and other properties to help identify certain device or service categories.
This makes Shodan useful for external exposure discovery.
Do Not Search Only by Port
One of the important lessons from Shodan’s own documentation is that searching for a single port is not necessarily a reliable way to identify a particular technology.
A service associated with an industrial protocol may appear on a nonstandard port, while the same port may also be used by unrelated services.
Shodan recommends using richer search properties such as product, operating system, tags and protocol specific information where possible.
The lesson is broader than Shodan:
A single technical indicator should not be treated as proof of asset identity.
Validate Before Reporting an Exposed OT Asset
External intelligence can contain stale information.
An IP address may have changed ownership. A hostname may point to a cloud service. A device may have been decommissioned after the last indexing event.
Therefore, an external assessment should validate important findings before presenting them as confirmed organizational exposure.
| Observation | Validation Question |
|---|---|
| Public IP | Does the address belong to the organization? |
| Hostname | Is the hostname associated with the organization? |
| Industrial service | Is the service actually associated with an OT asset? |
| Certificate | Does the certificate establish a meaningful relationship? |
| Open port | What service is actually responding? |
| Historical result | Is the exposure still present? |
Check Whether the Exposure Is Intended
Not every public service is necessarily an accidental exposure.
An organization may intentionally publish a remote access gateway or web service for a legitimate business or operational purpose.
The assessment should therefore ask:
- Is the service required?
- Who uses it?
- Why must it be Internet accessible?
- Is it isolated from sensitive OT systems?
- Are strong authentication controls applied?
- Is access monitored?
- Can the service be restricted further?
CISA’s Internet Exposure Reduction guidance follows the same principle: first identify Internet accessible assets, then determine whether exposure is necessary and remove or restrict unnecessary exposure.
Look for Industrial Control System Indicators
External discovery platforms may identify characteristics associated with industrial systems.
These indicators can include product information, service banners, protocol characteristics or other metadata that suggests an industrial device or service.
Shodan, for example, uses an ICS tag for services it identifies as industrial control systems.
However, an automated classification should still be validated before being used as the basis of a formal finding.
Look for Remote Access Infrastructure
Remote access deserves particular attention because it can provide a legitimate path toward internal systems while also creating an external attack surface.
The assessment should identify externally visible:
- VPN gateways
- Remote desktop services
- Remote support platforms
- Vendor access portals
- Web based management interfaces
- Remote monitoring systems
The presence of a remote access service does not prove that internal OT systems are reachable through it. That relationship requires separate validation.
Review Historical Exposure
An asset that is no longer exposed may still provide useful historical information.
Historical data can help answer questions such as:
- When did the service first become visible?
- How long was it exposed?
- Was the service removed?
- Did the product or software version change?
- Did the organization’s external footprint change after remediation?
Shodan provides historical information for IP addresses and its Trends functionality can be used to study historical exposure patterns.
Understand the Difference Between Exposure and Vulnerability
Consider three possible findings.
| Finding | What It Means |
|---|---|
| Publicly visible service | The Internet can identify or reach the service. |
| Known vulnerable software | The service may contain a known security weakness. |
| Confirmed exploitable condition | There is evidence supporting exploitation under defined conditions. |
These are different findings and should not be reported as though they are equivalent.
Do Not Exploit Publicly Exposed Industrial Systems Just to Prove a Point
An external attack surface assessment can often provide enough evidence without actively attempting to compromise the discovered system.
If a public service clearly identifies itself as an industrial device, that may already be sufficient evidence to recommend an exposure review.
Attempting authentication, changing configuration, sending protocol commands or otherwise interacting with an industrial system can create unnecessary risk and should not be performed without explicit authorization and an appropriate testing plan.
The safest assessment principle is simple: collect the evidence required to answer the security question without creating unnecessary operational impact.
Map External Exposure Back to the Internal Architecture
An external finding becomes much more meaningful when it can be connected to the organization’s internal architecture.
For example, an externally visible VPN gateway may be legitimate and well protected. The important question becomes what network zones and systems that gateway can reach.
Similarly, an Internet visible web interface may belong to a business system rather than an OT asset.
The assessment should therefore connect:
- External asset
- Internal owner
- Business or operational function
- Network zone
- Accessible service
- Authentication mechanism
- Potential path toward OT systems
Prioritize Internet Exposures
Not every exposed asset requires the same response.
| Priority | Example | Typical Action |
|---|---|---|
| Critical | Confirmed Internet exposed industrial service with unnecessary public access. | Investigate immediately and remove or restrict exposure where operationally possible. |
| High | Public remote access service providing a path toward sensitive OT systems. | Review architecture, authentication and access restrictions. |
| High | Known vulnerable Internet exposed service. | Validate the asset and apply appropriate remediation or compensating controls. |
| Medium | Unnecessary public service on supporting infrastructure. | Remove or restrict the service. |
| Lower | Stale historical exposure no longer present. | Document and verify that remediation remains effective. |
Priority should always be adjusted according to asset criticality, actual exposure, known exploitation, available controls and operational consequences.
Reduce the External Attack Surface
Once unnecessary exposure is identified, the strongest remediation is often simple: remove it.
CISA’s Internet Exposure Reduction guidance recommends determining which assets actually need Internet accessibility and restricting or removing exposure where it is not operationally necessary.
For services that must remain exposed, CISA recommends measures such as changing default passwords, keeping systems updated, using a secure monitored jump host, monitoring ingress and egress traffic and implementing MFA where possible.
Consider Monitoring for New Exposure
External exposure is not a one time problem.
A new firewall rule, cloud deployment, remote access service or network change can create exposure after the original assessment has finished.
For that reason, organizations should consider recurring external attack surface monitoring.
Shodan, for example, provides network monitoring and alerting capabilities that can identify newly observed services on monitored networks.
The important operational objective is not simply receiving alerts. It is establishing a process for validating and responding to unexpected exposure.
What a Professional OT External Attack Surface Assessment Should Deliver
A useful assessment should give the organization a defensible picture of what appears to be visible from the public Internet.
- External asset inventory
- Public IP and domain relationships
- Internet accessible services
- Industrial service indicators
- Remote access exposure
- Certificate and DNS observations
- Potentially vulnerable exposed services
- Historical exposure where available
- Asset ownership validation
- Exposure classification
- Risk prioritized findings
- Recommended remediation actions
Each finding should clearly identify the evidence source, observation, validation status, business or operational context and recommended action.
Example External Exposure Finding
| Finding Element | Example |
|---|---|
| Observation | An Internet search platform identifies an industrial service associated with an organization controlled IP range. |
| Validation | The IP range and service ownership are confirmed with the organization. |
| Exposure | The service is reachable from the public Internet. |
| Context | The organization confirms that public exposure is not required for the operational function. |
| Risk | Unnecessary external exposure increases the attack surface. |
| Recommendation | Remove public exposure and provide controlled access through an appropriate architecture if remote access is required. |
This is stronger than reporting “Shodan found a PLC” without validating ownership, current exposure or operational necessity.
Common OT External Attack Surface Mistakes
- Assuming the public IP inventory is complete.
- Searching only by port number.
- Treating Shodan results as automatically accurate.
- Failing to validate asset ownership.
- Confusing exposure with compromise.
- Confusing exposure with vulnerability.
- Ignoring historical data.
- Ignoring remote access infrastructure.
- Attempting unauthorized exploitation.
- Failing to connect external findings to internal architecture.
- Fixing a service without checking whether another dependency exists.
- Performing an assessment once and never monitoring for changes.
External Attack Surface Assessment Workflow
- Define the authorized scope.
- Collect known public IP ranges and domains.
- Identify related DNS and certificate information.
- Review Internet search and discovery platforms.
- Identify potentially exposed services.
- Identify possible industrial or remote access indicators.
- Validate ownership and current exposure.
- Compare exposure with the organization’s intended architecture.
- Determine whether each exposure is operationally necessary.
- Identify vulnerabilities or configuration concerns where evidence supports them.
- Prioritize findings according to risk.
- Recommend removal, restriction or additional controls.
- Establish recurring external exposure monitoring where appropriate.
Final Perspective
An OT external attack surface assessment is not about searching the Internet for interesting industrial devices.
It is about helping an organization understand what its own infrastructure appears to expose to the public Internet and whether those exposures are intentional, necessary and adequately protected.
Tools such as Shodan can provide valuable visibility, but the tool is only the beginning. The important work is validating the result, connecting it to the correct asset, understanding the operational purpose and deciding whether the exposure should exist.
The strongest remediation is often to remove unnecessary Internet exposure. Where external connectivity is genuinely required, it should be placed behind appropriate security controls, monitored and reviewed regularly.
For industrial organizations, knowing what the Internet can see is a practical first step toward reducing unnecessary attack surface.
Need an Independent OT External Attack Surface Assessment?
Cautivra provides focused external attack surface assessments for organizations that need to identify publicly visible industrial systems, remote access infrastructure, exposed services and other Internet facing assets.
The assessment uses authorized external reconnaissance and OSINT techniques to identify and validate exposure without attempting unauthorized compromise of industrial systems.
Request an OT Attack Surface Assessment
Sources and Further Reading
- CISA Internet Exposure Reduction Guidance
- CISA guidance on Internet exposed ICS and OT assets
- NIST SP 800-82 Rev. 3, Guide to Operational Technology Security
- Shodan official documentation
- CISA Known Exploited Vulnerabilities Catalog
