Skip to content

Commit e3cbf85

Browse files
author
Jill Grant
authored
Merge pull request #269770 from HollyCl/deploy_order321
updated concept articles for security and deployment order
2 parents 73a2de2 + cc094c2 commit e3cbf85

File tree

3 files changed

+23
-32
lines changed

3 files changed

+23
-32
lines changed

articles/operator-5g-core/concept-deployment-order.md

Lines changed: 12 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: HollyCl
66
ms.service: azure-operator-5g-core
77
ms.custom: devx-track-azurecli
88
ms.topic: concept-article #required; leave this attribute/value as-is.
9-
ms.date: 03/07/2024
9+
ms.date: 03/21/2024
1010

1111
#CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
1212
---
@@ -15,26 +15,20 @@ ms.date: 03/07/2024
1515

1616
Mobile Packet Core resources have minimal ordering constraints. To bring up network functions, the cluster services must be already running successfully. The same set of cluster services can be reused for multiple network functions and the cluster services must be deployed on every cluster that hosts the network functions.
1717

18-
## Azure CLI commands used to deploy resources
18+
## Mobile Packet Core resource deployment order
1919

20-
Use the following Azure CLI commands to deploy resources.
20+
Deploy resources in the following order. Note that the Microsoft.MobilePacketCore/clusterServices resource must be deployed first. All other resources can be deployed in any order or in parallel.
2121

22-
```azurecli
23-
{
24-
[
25-
Microsoft.MobilePacketCore/clusterServices
26-
],
27-
[
28-
Microsoft.MobilePacketCore/amfDeployments
29-
Microsoft.MobilePacketCore/smfDeployments
30-
Microsoft.MobilePacketCore/nrfDeployments
31-
Microsoft.MobilePacketCore/nssfDeployments
32-
Microsoft.MobilePacketCore/upfDeployments
33-
Microsoft.MobilePacketCore/observabilityServices
34-
]
35-
```
22+
Microsoft.MobilePacketCore/clusterServices
23+
Microsoft.MobilePacketCore/amfDeployments
24+
Microsoft.MobilePacketCore/smfDeployments
25+
Microsoft.MobilePacketCore/nrfDeployments
26+
Microsoft.MobilePacketCore/nssfDeployments
27+
Microsoft.MobilePacketCore/upfDeployments
28+
Microsoft.MobilePacketCore/observabilityServices
29+
3630

3731
## Related content
3832

39-
- [Complete the prerequisites to deploy Azure Operator 5G Core Preview on Azure Kubernetes Service] (quickstart-complete-prerequisites-deploy-azure-kubernetes-service.md)
33+
- [Complete the prerequisites to deploy Azure Operator 5G Core Preview on Azure Kubernetes Service](quickstart-complete-prerequisites-deploy-azure-kubernetes-service.md)
4034
- [Complete the prerequisites to deploy Azure Operator 5G Core Preview on Nexus Azure Kubernetes Service](quickstart-complete-prerequisites-deploy-nexus-azure-kubernetes-service.md)

articles/operator-5g-core/concept-security.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,20 @@
11
---
22
title: Security in Azure Operator 5G Core Preview
3-
description: Review the security features embedded in Azure Operator 5G Core Preview
3+
description: Review the security features embedded in Azure Operator 5G Core Preview.
44
author: SarahBoris
55
ms.author: sboris
66
ms.service: azure-operator-5g-core
77
ms.topic: concept-article #required; leave this attribute/value as-is.
8-
ms.date: 03/07/2024
8+
ms.date: 03/21/2024
99
---
1010

1111
# Security in Azure Operator 5G Core Preview
1212

13-
Microsoft is built on Zero Trust security, including Azure Operator 5G Core Preview. Rather than assuming that everything behind the corporate firewall is safe, Zero Trust assumes an open environment where trust must always be validated. Zero Trust is equally applied to all workload environments, both on Nexus and on Azure.
13+
Microsoft is built on Zero Trust security, including Azure Operator 5G Core Preview. Rather than assuming that everything behind the operator firewall is safe, Zero Trust assumes an open environment where trust must always be validated. Zero Trust is equally applied to all workload environments, both on Nexus and on Azure.
1414

15-
Zero Trust follows Azure Operator 5G Core from development through deployment and monitoring.
15+
Zero Trust follows Azure Operator 5G Core from development through deployment and runtime protection.
16+
17+
The Azure Operator 5G Core security posture is designed and built to prevent, detect, and defend against the latest security threats.
1618

1719
## Development
1820

@@ -30,15 +32,12 @@ Azure Operator 5G Core is deployed based on a security blueprint that ensures th
3032
- Least access privilege based on Role-based Access Control (RBAC) methodology.
3133
- Centralized Identity / Privilege Management using Microsoft Entra ID.
3234
- Secure transport to Azure through Express Route.
33-
- Encryption of traffic within the NFs and between NFs (3GPP).
35+
- Encryption of traffic both within network functions (NFs) and between NFs (3GPP).
3436
- Secure storage of data at rest.
3537

36-
## Monitoring
37-
38-
Security monitoring of the application occurs through a combination of native alerting from the NF and Azure security applications. It includes:
38+
## Runtime protection
3939

40-
- Security Logging - Visibility for actions internal to the application.
41-
- Microsoft Defender – Optional protection from cyber threats and vulnerabilities.
40+
Security monitoring of the application occurs through a combination of native alerting from the NF and Azure security applications, including security logging, which allows for the visibility of actions internal to the application.
4241

4342
## Related content
4443

articles/operator-5g-core/tutorial-configure-network-function.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: HollyCl
55
ms.author: HollyCl
66
ms.service: azure-operator-5g-core
77
ms.topic: tutorial #required; leave this attribute/value as-is
8-
ms.date: 02/22/2024
8+
ms.date: 03/21/2024
99

1010
---
1111

@@ -19,9 +19,7 @@ This article describes how to configure a network function following deployment.
1919

2020
## Configure a Session Management Function (SMF)
2121

22-
Use the procedures described in:
23-
- [SMF Configuration](https://manuals.metaswitch.com/UC/4.3.0/UnityCloud_Overview/Content/NetworkFunctions/SMF/SMF_configuration.htm)
24-
- [Interface Manager Configuration](https://manuals.metaswitch.com/UC/4.3.0/UnityCloud_Overview/Content/Microservices/SMF_Specific/Config/interface_mgr-cna-interface-mgr_config.html)
22+
Use the procedures described in [SMF Configuration](https://manuals.metaswitch.com/UC/4.3.0/UnityCloud_Overview/Content/NetworkFunctions/SMF/SMF_configuration.htm)
2523

2624
## Configure a User Plane Function (UPF)
2725

0 commit comments

Comments
 (0)