You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operator-5g-core/concept-deployment-order.md
+12-18Lines changed: 12 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: HollyCl
6
6
ms.service: azure-operator-5g-core
7
7
ms.custom: devx-track-azurecli
8
8
ms.topic: concept-article #required; leave this attribute/value as-is.
9
-
ms.date: 03/07/2024
9
+
ms.date: 03/21/2024
10
10
11
11
#CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
12
12
---
@@ -15,26 +15,20 @@ ms.date: 03/07/2024
15
15
16
16
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.
17
17
18
-
## Azure CLI commands used to deploy resources
18
+
## Mobile Packet Core resource deployment order
19
19
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.
21
21
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
+
36
30
37
31
## Related content
38
32
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)
40
34
-[Complete the prerequisites to deploy Azure Operator 5G Core Preview on Nexus Azure Kubernetes Service](quickstart-complete-prerequisites-deploy-nexus-azure-kubernetes-service.md)
Copy file name to clipboardExpand all lines: articles/operator-5g-core/concept-security.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,20 @@
1
1
---
2
2
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.
4
4
author: SarahBoris
5
5
ms.author: sboris
6
6
ms.service: azure-operator-5g-core
7
7
ms.topic: concept-article #required; leave this attribute/value as-is.
8
-
ms.date: 03/07/2024
8
+
ms.date: 03/21/2024
9
9
---
10
10
11
11
# Security in Azure Operator 5G Core Preview
12
12
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.
14
14
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.
16
18
17
19
## Development
18
20
@@ -30,15 +32,12 @@ Azure Operator 5G Core is deployed based on a security blueprint that ensures th
30
32
- Least access privilege based on Role-based Access Control (RBAC) methodology.
31
33
- Centralized Identity / Privilege Management using Microsoft Entra ID.
32
34
- 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).
34
36
- Secure storage of data at rest.
35
37
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
39
39
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.
Use the procedures described in [SMF Configuration](https://manuals.metaswitch.com/UC/4.3.0/UnityCloud_Overview/Content/NetworkFunctions/SMF/SMF_configuration.htm)
0 commit comments