Skip to content

Commit f57da6c

Browse files
committed
update
1 parent 759e566 commit f57da6c

File tree

3 files changed

+19
-143
lines changed

3 files changed

+19
-143
lines changed

articles/payment-hsm/deployment-scenarios.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,6 @@ This scenario caters to regional-level failure. The usual strategy is to complet
4040

4141
## Next steps
4242

43-
## Next steps
44-
4543
- [What is Azure Payment HSM?](overview.md)
4644
- [Azure Payment HSM solution design](solution-design.md)
4745
- [Azure Payment HSM traffic inspection](traffic-inspection.md)

articles/payment-hsm/inspect-traffic.md

Lines changed: 19 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Access the payShield manager for your Azure Payment HSM
3-
description: Access the payShield manager for your Azure Payment HSM
2+
title: Azure Payment HSM traffic inspection
3+
description: Azure Payment HSM traffic inspection
44
services: payment-hsm
55
ms.service: payment-hsm
66
author: msmbaldwin
@@ -9,53 +9,33 @@ ms.topic: quickstart
99
ms.date: 04/06/2023
1010
---
1111

12-
# How to inspect Azure Payment HSM traffic
12+
# Azure Payment HSM traffic inspection
1313

14-
Intent of this article is to explain how to inspect traffic to Azure Payment HSM.
15-
16-
Payment Hardware Security Module (Payment HSM or PHSM) is a [bare-metal service](overview.md) providing cryptographic key operations for real-time and critical payment transactions in the Azure cloud.
17-
18-
Payment HSM devices are a variation of Dedicated HSM devices with more advanced cryptographic modules and features: a Payment HSM never decrypts the PIN value in transit for example.
19-
20-
The Azure Payment HSM solution uses hardware from [Thales](https://cpl.thalesgroup.com/encryption/hardware-security-modules/payment-hsms/payshield-10k) as a vendor. Customers have [full control and exclusive access](overview.md#customer-managed-hsm-in-azure) to the Payment HSM.
21-
22-
## Azure Payment HSM - Networking
14+
Azure Payment Hardware Security Module (Payment HSM or PHSM) is a [bare-metal service](overview.md) providing cryptographic key operations for real-time and critical payment transactions in the Azure cloud. For more information, see [What is Azure Payment HSM?](overview.md).
2315

2416
When Payment HSM is deployed, it comes with a host network interface and a management network interface. There are several deployment scenarios:
17+
2518
1. [With host and management ports in same VNet](create-payment-hsm.md?tabs=azure-cli)
2619
2. [With host and management ports in different VNets](create-different-vnet.md?tabs=azure-cli)
2720
3. [With host and management port with IP addresses in different VNets](create-different-ip-addresses.md?tabs=azure-cli)
2821

2922
In all of the above scenarios, Payment HSM is a VNet-injected service in a delegated subnet: `hsmSubnet` and `managementHsmSubnet` must be delegated to `Microsoft.HardwareSecurityModules/dedicatedHSMs` service.
3023

31-
## FastPathEnabled feature flag & fastpathenabled VNet tag
32-
33-
In addition, the `FastPathEnabled` **feature** must be [registered and approved](https://learn.microsoft.com/en-us/azure/payment-hsm/register-payment-hsm-resource-providers?tabs=azure-cli#register-the-resource-providers-and-features) on all subscriptions that need access to Payment HSM.
34-
35-
A second step consists in enabling the `fastpathenabled` **tag** on the VNet hosting the Payment HSM delegated subnet and on every peered VNet requiring [connectivity to the Payment HSM devices](https://learn.microsoft.com/en-us/azure/payment-hsm/peer-vnets?tabs=azure-cli). This operation must be done via CLI.
36-
37-
For the `fastpathenabled` VNet tag to be valid, the `FastPathEnabled` feature needs to be enabled on the subscription where that VNet is deployed: make sure to complete both steps to enable resources to connect to the Payment HSM devices.
38-
39-
Adding the `FastPathEnabled` feature and enabling the `fastpathenabled` tag don't cause any downtime.
40-
41-
The public documentation related to these 2 settings is now available [here](fastpathenabled.md).
42-
43-
## Azure Payment HSM - Networking limitations
44-
4524
Payment HSM comes with some policy [restrictions](solution-design.md#constraints) on these subnets: **Network Security Groups (NSGs) and User-Defined Routes (UDRs) are currently not supported**.
4625

47-
> Note: PHSM is not compatible with vWAN topologies or cross region VNet peering, as listed in the [topology supported](solution-design.md#supported-topologies).
26+
> [!IMPORTANT]
27+
> The `FastPathEnabled` **feature** must be [registered and approved](register-payment-hsm-resource-providers.md?tabs=azure-cli#register-the-resource-providers-and-features) on all subscriptions that need access to Payment HSM. For more information, see [FastPathEnabled](fastpathenabled.md).
28+
29+
PHSM is not compatible with vWAN topologies or cross region VNet peering, as listed in the [topology supported](solution-design.md#supported-topologies).
4830

4931
This article present two ways to inspect traffic destined to a Payment HSM: a firewall with source network address translation (SNAT), and a firewall with reverse proxy
5032

51-
# Firewall with source network address translation (SNAT)
33+
## Firewall with source network address translation (SNAT)
5234

53-
This design is inspired by the [Dedicated HSM solution architecture](networking.md#solution-architecture).
35+
This design is inspired by the [Dedicated HSM solution architecture](../dedicated-hsm/networking.md#solution-architecture).
5436

5537
The firewall **SNATs the client IP address** before forwarding traffic to the PHSM NIC, guaranteeing that the return traffic will automatically be directed back to the Firewall. Either an Azure Firewall or a 3rd party FW NVA can be used in this design.
5638

57-
![image](docs/solution1fp.png)
58-
5939
:::image type="content" source="./media/firewall-snat-architecture-diagram.png" alt-text="Architecture diagram of the firewall with SNAT":::
6040

6141
Route tables required:
@@ -117,4 +97,11 @@ Results:
11797
- Filtering rules that cannot be enforced using NSGs on the PHSM subnet can be configured on the Firewall and/or on NSGs applied to the reverse proxy subnet.
11898
- Both Spoke traffic and On-Prem traffic to the PHSM environment are secured.
11999

120-
## Next steps
100+
## Next steps
101+
102+
- [What is Azure Payment HSM?](overview.md)
103+
- [Azure Payment HSM solution design](solution-design.md)
104+
- [Azure Payment HSM deployment scenarios](deployment-scenarios.md)
105+
- [Get started with Azure Payment HSM](getting-started.md)
106+
- [Create a payment HSM](create-payment-hsm.md)
107+
- [Frequently asked questions](faq.yml)

articles/payment-hsm/traffic-inspection.md

Lines changed: 0 additions & 109 deletions
This file was deleted.

0 commit comments

Comments
 (0)