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/hdinsight/domain-joined/hdinsight-security-overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ To access Apache Ranger and Ambari audit logs, and ssh access logs, [enable Azur
51
51
52
52
Protecting data is important for meeting organizational security and compliance requirements. Along with restricting access to data from unauthorized employees, you should encrypt it.
53
53
54
-
HDInsight supports data encryption at rest with both platform managed and [customer managed keys](../disk-encryption.md). Encryption of data in transit is handled with both TLS and IPSec. See [Encryption in transit for Azure HDInsight](encryption-in-transit.md) for more information.
54
+
HDInsight supports data encryption at rest with both platform managed and [customer managed keys](../disk-encryption.md). Encryption of data in transit is handled with both TLS and IPsec. See [Encryption in transit for Azure HDInsight](encryption-in-transit.md) for more information.
55
55
56
56
### Compliance
57
57
@@ -71,7 +71,7 @@ The following table provides links to resources for each type of security soluti
71
71
|| Enable the ["Secure transfer required"](../../storage/common/storage-require-secure-transfer.md) property on storage accounts. | Customer |
|| Configure [Azure virtual network service endpoints](../../virtual-network/virtual-network-service-endpoints-overview.md) for Azure Cosmos DB and [Azure SQL DB](/azure/azure-sql/database/vnet-service-endpoint-rule-overview)| Customer |
74
-
|| Ensure that the [Encryption in transit](./encryption-in-transit.md) feature is enabled to use TLS and IPSec for intra-cluster communication. | Customer |
74
+
|| Ensure that the [Encryption in transit](./encryption-in-transit.md) feature is enabled to use TLS and IPsec for intra-cluster communication. | Customer |
|| Control access to your data by Azure support using [Customer lockbox](../../security/fundamentals/customer-lockbox-overview.md)| Customer |
77
77
| Application and middleware security | Integrate with Microsoft Entra Domain Services and [Configure ESP](apache-domain-joined-configure-using-azure-adds.md) or use [HIB for OAuth Authentication](identity-broker.md)| Customer |
@@ -83,7 +83,7 @@ The following table provides links to resources for each type of security soluti
83
83
| Network security | Configure a [virtual network](../hdinsight-plan-virtual-network-deployment.md)|
84
84
|| Configure [Inbound network security group (NSG) rules](../control-network-traffic.md) or [private link](../hdinsight-private-link.md)| Customer |
85
85
|| Configure [Outbound traffic restriction](../hdinsight-restrict-outbound-traffic.md) with Firewall | Customer |
86
-
|| Configure [IPSec encryption in transit](encryption-in-transit.md) between cluster nodes | Customer |
86
+
|| Configure [IPsec encryption in transit](encryption-in-transit.md) between cluster nodes | Customer |
0 commit comments