External Attack Surface Management: Protecting Your Organization in the Digital Age

Explore how External Attack Surface Management (EASM) secures your digital assets and how CTM360 HackerView strengthens your cybersecurity strategy.
By
CTM360 Team
October 9, 2024
1 mins read
External Attack Surface Management: Protecting Your Organization in the Digital Age
background-graphics

What’s on this page

Overview
CTM360’s observation of the trend
Recommendations

In an increasingly interconnected digital world, organisations face a growing number of cyber threats. As businesses expand their online presence, their attack surface increases, making it more vulnerable to cyberattacks. This is where External Attack Surface Management (EASM) comes into play.

In this blog, we will explore the concept of EASM, what it includes, its importance, how it differs from security ratings, and what the future holds for this crucial aspect of cybersecurity. Additionally, we’ll discuss how CTM360 HackerView can help your organisation effectively manage its external attack surface.

What is EASM?

External Attack Surface Management (EASM) involves the continuous discovery, monitoring, and management of an organisation’s external-facing digital assets. These assets include websites, IP addresses, cloud services, and any other publicly accessible resources. A comprehensive EASM would also have the organisation’s mobile apps, genuine social media inventory, Executive Management profiles and more.  EASM focuses on first building a comprehensive “Digital Asset Register” and next identifying vulnerabilities and potential entry points that could be exploited by malicious actors. By gaining a deep understanding of the external attack surface, organisations can proactively mitigate risks and prevent breaches before they occur.

From the management perspective, EASM is an essential component of a robust cybersecurity strategy. It enables organisations to see their digital footprint from the perspective of an attacker, allowing them to identify and secure weak points that could be targeted.

What is Included in an Organization’s Attack Surface?

An organisation’s attack surface consists of all the external-facing digital assets that could potentially be targeted by cybercriminals. These include:

Domains, Hosts, and Sub-Domains:

An organization’s collection of domains, along with their associated hosts and sub-domains, creates numerous potential entry points for attackers. Each sub-domain may have unique vulnerabilities that can be exploited if not properly secured.

Web Applications:

Public-facing websites and web applications are common targets for attackers seeking to exploit vulnerabilities such as outdated software or weak authentication mechanisms.

Cloud Services:

With the rise of cloud computing, organisations often use cloud-based services for data storage and processing. Misconfigurations or insufficient security measures in these services can expose sensitive information.

IP Addresses:

Public IP addresses can be scanned by attackers to identify open ports or vulnerable services that can be exploited.

Third-Party Integrations:

Organisations often rely on third-party vendors or services that have access to their systems. These integrations can introduce additional vulnerabilities if not properly managed.SSL/TLS Certificates:

Weak or expired certificates can leave encrypted communications vulnerable to interception.

A comprehensive EASM solution would also include -

Inventory of Genuine Social Media Profiles:

An organisation's presence on social media platforms can be targeted by attackers for impersonation or phishing attempts.

Mobile Apps:

Attackers can create rogue mobile apps on third party stores to impersonate trusted brands, with the goal of gaining unauthorised access to information that can be used to commit fraudulent transactions.

Executive Management Names/Profiles:

Attackers may attempt to impersonate an organisation's executive leadership for social engineering attacks.

BIN Numbers:

Payment card information, including BIN (Bank Identification Number) data, can be exposed and used for fraudulent activities.

Environments & Technologies:

The list of technologies and their respective versions visible in the organisation's attack surface can help identify potential vulnerabilities and misconfigurations.

The attack surface also includes shadow IT, which refers to information technology systems implemented by departments outside of the central IT department to circumvent the limitations and restrictions set by the central information systems.

Why is EASM Important?

EASM is critical for several reasons:

1. Technology  consolidation

EASM promotes a unified security strategy, enabling organizations to consolidate their ever growing digital assets and stack of technologies and enhance the overall management of external cyber risk.

2. Reducing Attack Surface

Through continuous monitoring and assessment, EASM assists organizations in reducing their attack surface by proactively managing and securing external assets.

3. Proactive Risk Management:

EASM allows organisations to identify vulnerabilities before they are exploited. By continuously monitoring the attack surface, organisations can address security gaps promptly, reducing the likelihood of a successful attack.

4. Real-Time Visibility:

Cyber threats are constantly evolving, and new vulnerabilities emerge regularly. EASM provides real-time visibility into an organisation’s external assets, ensuring that security teams are always aware of the current state of the attack surface.

5. Regulatory Compliance:

Many industries are subject to strict regulatory requirements regarding data protection and cybersecurity. EASM helps organisations maintain compliance by ensuring that all external assets are properly secured.

6. Cost Efficiency:

Preventing a cyberattack is often far less expensive than dealing with the aftermath of a breach. EASM enables organisations to allocate resources more efficiently by prioritising the most critical vulnerabilities.

How is EASM Different from Security Ratings?

While both EASM and security ratings play a role in assessing an organisation’s cybersecurity posture, they serve different purposes and offer distinct benefits:

1. Scope of Analysis:

Security ratings are typically based on a broad assessment of an organisation’s overall security practices, often using data from public sources. EASM, on the other hand, focuses specifically on the external attack surface, providing a more detailed and targeted analysis of potential vulnerabilities.

2. Continuous Monitoring:

EASM involves continuous monitoring of external assets, offering real-time insights into the attack surface. Security ratings are often static, providing a snapshot of an organisation’s security posture at a specific point in time.

3. Actionable Insights:

EASM provides actionable insights that organisations can use to address specific vulnerabilities. Security ratings are more generalised and may not offer the same level of detail needed to implement targeted security measures.

4. Perspective:

EASM approaches cybersecurity from the attacker’s perspective, identifying entry points and weaknesses that could be exploited. Security ratings focus on the organisation’s overall security practices and controls.

What Does the Future Hold?

As cyber threats continue to evolve, the importance of EASM will only grow. Organisations are increasingly adopting digital transformation strategies, expanding their digital footprints, and moving more services to the cloud. This expansion introduces new vulnerabilities, making EASM an essential component of any comprehensive cybersecurity strategy.

In the future, we can expect EASM tools and technologies to become more sophisticated, incorporating advanced AI and machine learning algorithms to identify and mitigate risks more effectively. The integration of EASM with other cybersecurity solutions, such as Security Information and Event Management (SIEM) and Endpoint Detection and Response (EDR), will provide organisations with a more holistic approach to managing their security posture.

How Can CTM360 HackerView Help?

CTM360’s HackerView is an innovative External Attack Surface Management (EASM) platform designed to give organisations a comprehensive understanding of their digital presence from an attacker’s perspective. By combining automated asset discovery, issue identification, remediation guidelines, security ratings, and third-party risk management, HackerView empowers businesses to proactively defend against potential cyber threats.

Here’s how CTM360 HackerView can significantly enhance your organisation's cybersecurity strategy:

1. Continuous & Automated Digital Asset Discovery

One of the most critical aspects of EASM is the ability to identify and map all external-facing digital assets. HackerView excels in this area by automatically discovering and mapping your organisation’s digital footprint. Operating in a passive and non-intrusive manner, it leverages data available in the public domain to uncover assets that may otherwise be overlooked.

The platform comes pre-populated, ensuring that from the moment you start using it, you have a comprehensive view of your digital assets. This includes websites, IP addresses, cloud services, and more. Automated discovery ensures that no asset is left unmonitored, reducing the risk of shadow IT and other unsecured entry points.

One of the key advantages of HackerView is how often it continuously discovers, updates, and refreshes all assets belonging to the organisation. The platform automatically updates its inventory of digital assets every 24-48 hours, ensuring that your security team has access to the most current and complete information about your attack surface.

2. Comprehensive Digital Risk Scorecard

HackerView provides a detailed digital risk scorecard that assesses your organisation’s visible cyber vulnerabilities. This scorecard is essential for understanding your current security posture and identifying areas that require immediate attention. The scorecard is updated continuously, allowing you to track improvements or new risks as they emerge.

3. Detailed Inventory of Digital Assets

Understanding what you have is the first step toward protecting it. HackerView provides a detailed inventory of your digital assets, allowing you to keep track of all external-facing resources. This inventory is continually updated as new assets are discovered or changes are made, ensuring that your records are always accurate and up-to-6.

4. Remediation Plans & Ongoing Guidance

Identifying vulnerabilities is only half the battle; addressing them effectively is the key to maintaining a robust security posture. HackerView not only identifies issues but also provides detailed remediation plans and ongoing guidance. These plans are tailored to your specific vulnerabilities, offering step-by-step instructions on how to address each issue.

5. Third-Party Risk Monitoring

In today’s interconnected world, organisations rely heavily on third-party vendors and partners. However, these relationships can introduce additional risks if not properly managed. HackerView’s third-party risk monitoring feature allows you to assess the security posture of your vendors, partners, and other third parties with whom you share data or systems.

6. Pre-built and Custom Portfolios

The platform allows you to access pre-built portfolios that include entities from important industry sectors within your geographic region. This allows you to benchmark your organisation's cybersecurity posture against your peers, gaining valuable insights into how you measure up. Additionally, you can create custom portfolios of your key vendors and third-party providers, continuously tracking their security health and potential vulnerabilities.

In conclusion, as organisations continue to navigate the complexities of the digital landscape, EASM will remain a vital component of cybersecurity. By leveraging advanced tools like CTM360 HackerView, businesses can protect their digital assets, stay ahead of potential threats and ensure the security of their operations.

Recent Blogs

Overview

The fight against email-based threats is intensifying. Following the lead of Google and Yahoo, Microsoft has officially announced the mandatory implementation of email authentication protocols, SPF, DKIM, and DMARC, for high-volume email senders, effective May 5, 2025. Domains sending over 5,000 daily emails to Microsoft's platforms, including Outlook.com, Hotmail.com, and Live.com, will be required to authenticate their messages. Initially, non-compliant messages will be redirected to recipients' Junk folders, with eventual total rejection expected if compliance isn't achieved. This enforcement represents a critical step in securing global email communications from spoofing and phishing threats (Microsoft Tech Community).

Understanding Email Authentication

Email authentication has become essential in combating increasingly sophisticated phishing and spoofing attacks. Three core standards have been adopted widely:

  • Sender Policy Framework (SPF: RFC 7208): Verifies the legitimacy of the sending mail server, ensuring messages originate from authorized infrastructure. SPF helps prevent sender address forgery by defining authorized sending sources in DNS records.
  • DomainKeys Identified Mail (DKIM: RFC 6376): Cryptographically signs email messages, allowing recipients to confirm message content hasn't been altered in transit. DKIM leverages public-private key pairs to ensure message integrity and authenticity.
  • Domain-based Message Authentication, Reporting, and Conformance (DMARC: RFC 7489): Combines SPF and DKIM to enforce domain alignment, verify authenticity, and provide reporting mechanisms for senders to track email usage and potential abuse. DMARC is recommended to be implemented in three incremental stages: initial monitoring (p=none), intermediate quarantining of suspicious messages to test the policy impact (p=quarantine), and full rejection of unauthorized emails to achieve DMARC compliance (p=reject). 

Email Content and Delivery Best Practice Guidance

To help the email ecosystem thrive and ensure that legitimate communications reach users' inboxes, major providers like Google, Yahoo, and Microsoft have released a unified set of technical and content-based requirements. This section consolidates these guidelines into a single resource for senders seeking to avoid spam filtering and maintain high deliverability rates.

1. Message Headers & Structural Integrity

Best Practice Description
Valid and consistent From header Use a single, clear email identity. Avoid multiple addresses in From and misleading sender names.
Aligned Reply-To domain Ensure Reply-To reflects the same domain or purpose as From.
Unique and compliant Message-ID Follow RFC 5322 formatting. Avoid duplicate or malformed IDs.
Proper MIME structure and header syntax Messages must conform to standard email formatting. Avoid malformed headers and nested MIME issues.
Avoid forged headers Do not spoof or misuse headers associated with major domains (e.g., gmail.com, outlook.com).

2. Content Hygiene and Formatting

Best Practice Description
Avoid deceptive subject lines Refrain from using misleading tags like "RE:" or "FWD:" unless applicable.
Balanced text-to-image ratio Do not send image-only emails. Include meaningful text with alt text for images.
Email size < 100 KB Ensure the email body stays within standard size limits (typically under 100 KB) to avoid clipping in mail clients. This refers only to the message content and does not include attachments.
Professional formatting Avoid ALL CAPS, excessive punctuation, invisible text, and non-standard fonts.
Exclude scripts and forms Embedded forms or JavaScript will trigger spam or phishing filters.
Consistent branding and tone Use recognizable logos, colors, and sender names to build trust.

3. Infrastructure and Technical Configuration

Best Practice Description
Valid PTR (reverse DNS) records The sending IP address must resolve to a valid hostname that maps back to the same IP address.
TLS for outbound SMTP TLS is mandatory for Gmail. Senders without encryption may be rejected.
SPF lookup limit adherence Keep SPF DNS lookups ≤ 10. Microsoft enforces this.
IP/domain warming Gradually increase send volume from new IPs or domains to build a reputation.
Consistent sending patterns Avoid sending bursts or erratic volumes. Maintain daily volume stability.
ARC headers for forwarded email ARC ensures original authentication results are preserved through intermediaries.

4. Recipient List Management

Best Practice Description
Explicit opt-in only Do not use purchased lists. Only email users who have explicitly subscribed.
Functional one-click unsubscribe Add RFC-compliant headers:
List-Unsubscribe: <https://domain/unsub?id=xyz>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
Unsubscribe fulfillment within 48 hours Honor removal requests promptly to reduce complaints.
List cleaning and bounce management Regularly purge unengaged, bounced, or invalid addresses.
Segmentation by message type Separate promotional, transactional, and notification content using distinct sender identities.

5. Engagement and Complaint Monitoring

Tool / Method Purpose
Google Postmaster Tools Monitor domain/IP reputation, spam rate, and user engagement.
Yahoo Complaint Feedback Loop (CFL) Receive ARF reports for complaints and unsubscribe flagged users.
Maintain a complaint rate < 0.3% High complaint rates trigger deliverability throttling and domain penalties.
Monitor bounce and open rates Use these to assess the health of your lists and campaigns.

6. Summary Recommendations

  1. Align headers and domains with clear, professional identities.
  2. Respect opt-in and unsubscribe behaviors with transparent mechanisms.
  3. Structure content to be clean, concise, and free of deceptive or spammy characteristics.
  4. Maintain technical hygiene through DNS, TLS, SPF limits, and ARC usage.
  5. Monitor sender reputation and user engagement continuously.

Immediate Impact and Risks of Non - compliance

As of May 2025, domains that fail SPF or DKIM checks or lack a correctly configured DMARC policy with alignment will risk having their emails marked as spam or not delivered at all. Misalignment occurs when the domain used in the message's "From" address doesn't match the domains authenticated by SPF or DKIM.

Organizations failing to comply face significant risks, including diminished deliverability rates, compromised customer trust, and increased susceptibility to impersonation attacks. These impacts directly affect an organization's reputation, customer engagement, and potentially, its revenue.

Actionable Recommendations for Immediate Implementation

To effectively prepare for these mandatory standards, organizations should:

  • Audit current DNS records: Utilize tools such as "dig" or Google DNS to verify SPF, DKIM, and DMARC records.
  • Begin with Monitoring (p=none): Initially deploy DMARC in monitoring mode to understand email flows and detect anomalies without risking legitimate email delivery.
  • Gradually enforce stricter policies: Move from quarantine to full rejection while monitoring.
  • Ensure domain alignment: "From" domain must match what’s authenticated via SPF or DKIM.
  • Maintain email hygiene: Clean lists, include a clear opt-out option, and avoid using misleading subject lines or headers.

Start Your DMARC Journey with CTM360 Free Community Edition

To support organizations navigating these changes, CTM360 offers a complimentary zero-cost Community Edition platform. It allows comprehensive monitoring, management, and enhancement of your DMARC records and email authentication setup. This proactive approach helps organizations reduce risks associated with impersonation attacks and maintain reliable email communication.

Join CTM360 Community Edition today, no hidden costs, simply real security.

Reference:

Disclaimer:

The information contained in this document is meant to provide general guidance and brief information to the intended recipient pertaining to the incident and recommended action. Therefore, this information is provided "as is" without warranties of any kind, express or implied, including accuracy, timeliness, and completeness.

Consequently, under NO condition shall CTM360®, its related partners, directors, principals, agents, or employees be liable for any direct, indirect, accidental, special, exemplary, punitive, consequential, or other damages or claims whatsoever including, but not limited to loss of data, loss in profits/business, network disruption...etc., arisina out of or in connection with this advisory.

For more information: Email: monitor@ctm360.com Tel: (973) 77 360 360

Summary:

In December 2024, hackers compromised at least 35 Google Chrome extensions, affecting approximately 2.6 million users. The attack exploited phishing emails sent to developers, masquerading as Google policy violation notices. These emails tricked developers into granting permissions to a malicious OAuth application named

“Privacy Policy Extension.

” Once authorized, the attackers gained control over the extensions, injecting malicious code to steal user data, particularly targeting Facebook credentials and business accounts. Browser extensions can significantly enhance productivity by adding new features to web browsers like Microsoft Edge and Google Chrome. However, they also pose significant security risks, as malicious or compromised extensions can lead to data breaches, malware infections, and unauthorized access to corporate networks. It is crucial for organizations to control, block, or manage browser extensions to minimize security risks, particularly in an enterprise environment. This advisory outlines the steps to block and protect browser extensions for Microsoft Edge and Google Chrome, and it also includes specific guidance on managing extensions using Microsoft Intune.

Risks Associated With Browser Extensions

Data Exposure: Some extensions can access sensitive data (e.g., browsing history, credentials, and files), potentially exposing confidential information.

Malicious Extensions: Cybercriminals can create or compromise extensions, making them a vector for malware distribution or data exfiltration.

Phishing Risks: Extensions may manipulate web content, tricking users into providing sensitive information.

Performance Degradation: Some poorly coded extensions can slow down browsers or degrade system performance.

Managing Browser Extensions Using Group Policy

A. Microsoft Edge

Using Group Policy (Windows)

1. Open the Group Policy Management Console (GPMC).

2. Navigate to:  Computer Configuration > Administrative Templates > Microsoft Edge > Extensions

3. Set the following policies:

a. Control which extensions are installed silently: Specify allowed extensions by adding their extension IDs.

b. Configure extension management settings: T o block all extensions, set this policy to "*" (deny all).

c. Configure the list of force-installed extensions: If any extension is necessary for business, add the corresponding extension ID here.

B. Google Chrome

Using Group Policy (Windows)

1. Open the Group Policy Editor.

2. Navigate to: Computer Configuration > Administrative Templates > Google > Google Chrome > Extensions

3. Set the following policies:

a. Block external extensions: Set the policy to block all extensions unless specifically allowed by adding the extension IDs.

b. Configure extension install allow list: If certain extensions are necessary, add their extension IDs here.

c. Configure extension install blocklist: Add a wildcard"*" to block all extensions.

Managing Browser Extensions Using Microsoft Intune

Organizations using Microsoft Intune for endpoint management can apply policies to control browser extension installations across all managed devices. This approach is particularly useful for managing large numbers of endpoints efficiently.

Blocking Extensions in Microsoft Edge Using Intune

1. Sign in to Microsoft Endpoint Manager Admin Center.

2. Navigate to: Devices > Configuration profiles > Create profile

3. Choose:

a. Platform: Windows 10 and later.

b. Profile type: Settings catalog.

4. In the Configuration settings, search for Extensions under Microsoft Edge:

a. Allow specific extensions to be installed (User): Specify allowed extension IDs

b. Control which extensions cannot be installed (User): Add a wildcard"*" to block all extensions.

5. Assign this profile to your target groups (specific users or devices).

Blocking Extensions in Google Chrome Using Intune

1. Sign in to Microsoft Endpoint Manager Admin Center.

2. Navigate to: Devices > Configuration profiles > Create profile

3. Choose:

a. Platform: Windows 10 and later.

b. Profile type: Settings catalog.

4. In the Configuration settings, search for Extensions under Google Chrome\Extensions:

a. Configure extension installation allow list (User): Specify allowed extension IDs

b. Configure extension installation blocklist: Add a wildcard"*" to block all extensions.

5. Assign this profile to your target groups (specific users or devices).

Note: These steps are mentioned for user-based controls. Similar configuration steps can be applied for device-based controls.

Best Practices for Managing Browser Extensions

Audit Extensions Regularly: Regularly audit the extensions installed on users’ browsers to detect unauthorized or risky extensions.

User Training: Educate users about the risks associated with browser extensions and how to identify malicious ones.

Implement a Zero-Trust Model: Always assume that extensions can potentially be compromised. Apply the principle of least privilege when granting extension permissions.

Use Security Solutions: Consider deploying security solutions that can monitor and block malicious browser activities, including suspicious extension behavior.

Conclusion

Controlling browser extensions in Microsoft Edge and Google Chrome is a critical aspect of securing enterprise endpoints. By implementing the steps outlined above, organizations can significantly reduce the risks associated with browser extensions. Whether you manage your endpoints using Group Policy or Microsoft Intune, these controls can help protect your network from potential extension-related threats. By following this advisory, organizations can take proactive steps to mitigate browser extension risks, enhancing their overall cybersecurity posture.

Reference:

https://www.bleepingcomputer.com/news/security/new-details-reveal-how-hackers-hijacked-35-google-chrome-extensions/

https://learn.microsoft.com/en-us/defender-endpoint/manage-profiles-approve-sys-extensions-intune

https://gbhackers.com/malicious-editthiscookie-extension/#google_vignette

Disclaimer

The information contained in this document is meant to provide general guidance and brief information to the intended recipient pertaining to the incident and recommended action. Therefore, this information is provided "as is" without warranties of any kind, express or implied, including accuracy, timeliness, and completeness. Consequently, under NO condition shall CTM360®, its related partners, directors, principals, agents, or employees be liable for any direct, indirect, accidental, special, exemplary, punitive, consequential, or other damages or claims whatsoever including, but not limited to: loss of data, loss in profits/business, network disruption…etc., arising out of or in connection with this advisory.

For more information:

Email: monitor@ctm360.com Tel: (+973) 77 360 360

There is an ongoing scam email campaign targeting executives from prominent organizations around the world. These reported email addresses on the domains are genuine email accounts of 'Virgin Media', 'Optimum' & 'Cox communications' users' which are compromised and sold on underground forums. Scammers buy and use such accounts as they have a higher reputation compared to newly created free accounts to bypass email gateways and spam filters and also lower their risk of being detected or tracked back in a bigger BEC attack.

These accounts are compromised by threat actors via phishing emails and malware, and the issue with such accounts will persist as long as end users are not careful enough while dealing with phishing and malicious emails. Based on our previous experience in response with the hosts Virgin Media, Optimum and Cox.net which are TV and cable providers in the UK and USA. They do not investigate email accounts reported to their abuse team without the original email and header information as this is a mandatory requirement as per their abuse policies. However, once this information is provided they do take action by resetting/recovering the reported account of the original user.

Additionally, enabling strict quarantine measures on your email gateway from these domains will make you a harder target and eventually the attackers moving on to another one.

RECOMMENDATIONS

  • As a precautionary measure, all email from private and/or external email addresses which contain the name of your executive staff in the "From" field may flagged.
  • As part of containment, please ensure to quarantine emails from the domain @virginmedia[.]com, @optimum[.]net, @optonline[.]net, @cox[.]net, @cox[.]com
  • As this type of email is tricky, it is highly recommended to conduct phishing awareness training for all employees to avoid potential risks.
//chatbot //Ahrefs