---
schema_version: "1"
id: 7ec0eda55fcc094aceb13fb9dcddc38ffe6758c7cd7c33b36d7e98bfded89065
title: Minimize the Attack Surface
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_minimize_the_attack_surface.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_minimize_the_attack_surface.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: dd652c2021319c805e2f59f150426385afec3fb79ea2ceae76b658f40b634b2a
description: To reduce overall risk in secure development, reduce the attack surface that’s exposed to potential attackers. Every port you open, every external library you use in your B2C Commerce code, and every user you give access to your data creates a new attack surface. To reduce the overall risk to the system, minimize the attack surface.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Minimize the Attack Surface

To reduce overall risk in secure development, reduce the attack surface that’s exposed to potential attackers. Every port you open, every external library you use in your B2C Commerce code, and every user you give access to your data creates a new attack surface. To reduce the overall risk to the system, minimize the attack surface.

Here are some examples.

- A server running unnecessary services such as FTP, SMB, and Telnet gives the attacker an opportunity to exploit a vulnerability in any of those listening services.
- A web API built with only HTTPS exposed on the server minimizes attackable ports and prevents eavesdropping.
- A feature that uses many third-party libraries in the code, some of which may be unnecessary, is vulnerable to potential issues in any of those libraries.