Skip to content

Commit 62b3714

Browse files
authored
Update overview.md
1 parent 1a7803b commit 62b3714

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/payment-hsm/overview.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,12 +22,16 @@ The Azure Payment HSM solution uses hardware from [Thales](https://cpl.thalesgro
2222
2323
## Azure payment HSM high-level architecture
2424

25-
After a Payment HSM is provisioned, the HSM device is connected directly to a customer's virtual network, with full remote HSM management capabilities, through Thales payShield Manager and the payShield Trusted Management Device (TMD).
25+
After a payment HSM is provisioned, the HSM device is connected directly to a customer's virtual network, with full remote HSM management capabilities, through Thales payShield Manager and the payShield Trusted Management Device (TMD).
2626

2727
Two host network interfaces and one management network interface are created at HSM provision.
2828

2929
:::image type="content" source="./media/high-level-architecture.png" lightbox="./media/high-level-architecture.png" alt-text="An architecture diagram, showing a provisioned Payment HSM and the network interfaces.":::
3030

31+
With the Azure Payment HSM provisioning service, customers have native access to two host network interfaces and one management interface on the payment HSM. This screenshot displays the Azure Payment HSM resources within a resource group.
32+
33+
:::image type="content" source="./media/portal-view-payment-hsms.png" lightbox="./media/high-level-architecture.png" alt-text="A screenshot illustrating that the owner of a payment HSM has access to two host network interfaces and one management interface.":::
34+
3135
## Why use Azure Payment HSM?
3236

3337
Momentum is building as financial institutions move some or all of their payment applications to the cloud, requiring a migration from the legacy on-premises applications and HSMs to a cloud-based infrastructure that isn't generally under their direct control. Often it means a subscription service rather than perpetual ownership of physical equipment and software. Corporate initiatives for efficiency and a scaled-down physical presence are the drivers for this shift. Conversely, with cloud-native organizations, the adoption of cloud-first without any on-premises presence is their fundamental business model. Whatever the reason, end users of a cloud-based payment infrastructure expect reduced IT complexity, streamlined security compliance, and flexibility to scale their solution seamlessly as their business grows.

0 commit comments

Comments
 (0)