Skip to content

Commit 87601cf

Browse files
authored
Merge pull request #7267 from laujan/484095-sfi-wave-6-security-horizontal
add new security article
2 parents dee7ccf + 5a4d5e8 commit 87601cf

File tree

2 files changed

+138
-2
lines changed

2 files changed

+138
-2
lines changed
Lines changed: 135 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,135 @@
1+
---
2+
title: Secure your Azure AI Translator data and deployment
3+
description: Learn how to secure Azure AI Translator, with best practices for protecting your data and deployment.
4+
author: laujan
5+
ms.author: lajanuar
6+
ms.service: azure-ai-translator
7+
ms.topic: conceptual
8+
ms.custom: horz-security
9+
ms.date: 09/25/2025
10+
---
11+
12+
# Security guidelines for Azure AI Translator
13+
14+
Azure AI Translator is a powerful cloud-based service designed to deliver real-time translation capabilities for a wide range of scenarios, including applications, websites, and business workflows. When organizations integrate this service, they can enhance global communication and user engagement across multiple languages and dialects.
15+
16+
* **Security within Azure is grounded in a collaborative model, where the responsibility for protecting resources and data is shared between Microsoft and our customers.**
17+
18+
* **Microsoft is dedicated to securing the core infrastructure that underpins all Azure services, providing a reliable and robust foundation for cloud operations.**
19+
20+
* **Our customers also play a crucial role in this security partnership by ensuring that Azure AI Translator is properly configured and managed, thereby protecting sensitive information and adhering to all relevant regulatory requirements.**
21+
22+
* **By clearly understanding and fulfilling their respective responsibilities, both Microsoft and our customers work together to achieve a comprehensive and resilient security posture in the Azure environment.**
23+
24+
* For more information, *see* [**Shared responsibility in the cloud**](/azure/security/fundamentals/shared-responsibility)
25+
26+
This document offers detailed guidelines and practical recommendations for establishing and maintaining a secure environment when using Azure AI Translator. It's essential for users of any service to prioritize the protection of sensitive data, safeguard user privacy, and ensure deployment reliability. By adhering to these best practices, you help reduce risks and guarantee that your translation solutions remain secure and effective across all platforms.
27+
28+
## Service-specific security
29+
30+
Azure AI Translator service requires careful consideration of specific security challenges and requirements to maintain the confidentiality and integrity of translation workflows. By taking a proactive approach to these security concerns, you can protect sensitive information during translation and reduce the risk of unauthorized access or data breaches.
31+
32+
* **Text translation**: For public-facing translation services, it's important to apply content filtering as necessary. Additionally, consider implementing extra filtering measures to prevent the translation of harmful or inappropriate content.<br>
33+
For more information, *see* [Prevent translation with the Translator service](/azure/ai-services/translator/prevent-translation).
34+
35+
* **Document translation**: When translating documents, ensure secure workflows are established. Utilize secure storage containers with appropriate access controls and encryption to safeguard both the original documents and the translated outputs.<br>
36+
For more information, *see* [What is Azure AI Document Translation?](/azure/ai-services/translator/document-translation/how-to-guides/use-rest-api-programmatically).
37+
38+
* **Custom translation**: To ensure the security of proprietary terminology and domain-specific language, it's important to set up robust access controls for custom translation models. By restricting access to both the models and their underlying training data, organizations can effectively protect sensitive linguistic assets.<br>
39+
For more information, *see* [Azure AI Custom Translator for beginners](/azure/ai-services/translator/custom-translator/beginners-guide).
40+
41+
* **Azure AI Translator containers**: For scenarios that require high security or offline translation in isolated environments, consider deploying Translator containers. This deployment model is well-suited for safeguarding sensitive data and supporting translation workflows in controlled or disconnected environments.<br>
42+
For more information, *see* [Azure AI Translator features and development options](/azure/ai-services/translator/overview#azure-ai-translator-features-and-development-options).
43+
44+
## Identity and access management
45+
46+
Effectively overseeing identities and access permissions is crucial for protecting your Azure AI Translator deployments from unauthorized use and possible credential compromise. By enforcing secure access management, you guarantee that only approved users and devices are able to interact with your Translator resource. The following list identifies ways you can support secure access management:
47+
48+
* **Access**. To effectively manage user identities and securely control access permissions for your Azure AI Translator resources, enable Microsoft Entra ID. By integrating Microsoft Entra ID, you can streamline the administration of user accounts and ensure that only authorized individuals have access to your Azure AI Translator services.<br>
49+
For more information, *see* [Enable Microsoft Entra ID authentication](/azure/ai-services/translator/how-to/microsoft-entra-id-auth)
50+
51+
* **Authorization**. Grant only the permissions that are essential for each role using role-based access control (RBAC). By utilizing RBAC-managed identities, you uphold the principle of least privilege, ensuring that users receive only the access required to perform their specific tasks. This approach greatly minimizes the possibility of unauthorized access to sensitive information or critical functions within your API.<br>
52+
For more information, *see* [Managed identities: role-based access control](/azure/ai-services/translator/document-translation/how-to-guides/create-use-managed-identities)
53+
54+
* **Authentication**. Access to Translator data should be limited solely to entities that successfully complete authentication. This restriction requires users to successfully complete verification and receive authorization before they can view or modify Translator data. Only users with proper approval gain access or editing privileges. This approach provides a layer of security by making certain that unauthorized users can't access sensitive information or make changes that could impact the integrity of the data.<br>
55+
For more information, *see* [Authentication and authorization](/azure/ai-services/translator/text-translation/reference/authentication)
56+
57+
* **Azure Key Vault**. Azure Key Vault offers a secure, centralized repository for application secrets like database connection strings, API keys, customer managed keys (CMK), passwords, and cryptographic keys. Using the key vault eliminates the need to hard-code sensitive information directly into application code or configuration files, reducing the risk of accidental exposure.<br>
58+
For more information, *see* [About Azure Key Vault](/azure/key-vault/general/overview).<br>
59+
For Custom Translator implementation, *see* [Encryption key management](/azure/ai-services/translator/custom-translator/concepts/encrypt-data-at-rest)<br><br>
60+
61+
> [!TIP]
62+
> ✔️ **Rotate API keys regularly**: Keys in Azure Key Vault can be configured with rotation policies that automatically generate new key versions at specified frequencies. Regularly rotating your Translator service API keys mitigates the risk of compromised credentials being used to access your services. For more information, *see* [Key autorotation](/azure/key-vault/general/autorotation).
63+
64+
## Network security
65+
66+
Azure AI Translator processes sensitive data from your applications. Therefore, it's essential to establish strong network isolation measures to prevent unauthorized access and ensure that translated content remains secure. The following list outlines key practices to help you manage secure access effectively:
67+
68+
* **Configure private endpoints**: Increase shielding by configuring private endpoints for API requests. This approach strengthens security and provides enhanced network isolation for your Azure AI Translator resources.<br>
69+
For more information, *see* [Use private endpoints with Azure AI services](/azure/ai-services/cognitive-services-virtual-networks#use-private-endpoints).
70+
71+
* **Implement virtual network service endpoints**: Augment safeguards by restricting network access to allow only traffic originating from your Azure virtual network. At the same time, ensure that you maintain optimal routing by utilizing the Microsoft backbone network for all communications.<br>
72+
For more information, *see* [Enable Azure AI Custom Translator through Azure Virtual Network](/azure/ai-services/translator/custom-translator/how-to/enable-vnet-service-endpoint).
73+
74+
* **Configure firewall rules**: Enhance security by designating specific IP addresses or ranges that are permitted to access your Translator resource. Restricting access in this way minimizes the likelihood of unauthorized connections from unfamiliar networks.<br>
75+
For more information, *see* [Use Azure AI Translator behind firewalls](/azure/ai-services/translator/how-to/use-firewalls#configure-firewall).
76+
77+
* **Use region-specific endpoints**: Bolster security and compliance by utilizing geographic endpoints. This approach ensures your traffic remains within designated regions and supports adherence to data residency regulations. For more information, *see* [Use Azure AI Translator behind firewalls](/azure/ai-services/translator/how-to/use-firewalls).
78+
79+
## Data protection
80+
81+
Azure AI Translator processes sensitive text and document content. Because of the confidential nature of this information, implementing robust data protection measures is essential. These safeguards are vital not only to maintain the privacy and confidentiality of the data being processed but also to ensure compliance with relevant regulations and industry standards.
82+
83+
* **Enable data encryption at rest**: Ensure your data is automatically encrypted with Federal Information Processing Standard (FIPS) 140-2 compliant 256-bit Advanced Encryption Standard (AES) when stored by the service.<br>
84+
For more information, *see* [Microsoft compliance](/compliance/regulatory/offering-fips-140-2).
85+
86+
* **Implement Customer-managed keys (CMK)**: To achieve enhanced control over encryption key management, configure customer-managed keys for Translator resources by integrating Azure Key Vault. This capability is accessible when selecting a pricing tier that includes support for customer-managed key functionality.<br>
87+
For more information, *see* [Azure AI Translator encryption of data at rest](/azure/ai-services/translator/custom-translator/concepts/encrypt-data-at-rest).
88+
89+
* **Review details of the No-Trace policy**: Translator doesn't retain customer data submitted for text translation; it processes the data without storing it. For document translation, data is stored only temporarily during processing and isn't kept afterward.<br>
90+
For more information, *see* [Data, privacy, and security for Azure AI Translator](/azure/ai-foundry/responsible-ai/translator/data-privacy-security).
91+
92+
* **Follow data residency requirements**: To ensure that your deployment adheres to regional data residency regulations, select the designated geographical endpoints for your Translator service. Use these endpoints to remain compliant with local requirements.<br>
93+
For more information, *see* [Use Azure AI Translator behind firewalls](/azure/ai-services/translator/how-to/use-firewalls).
94+
95+
## Logging and monitoring
96+
97+
Establishing robust logging and monitoring is critical for identifying potential security threats and resolving issues within your Azure AI Translator deployment. By ensuring that all relevant activities and anomalies are thoroughly tracked, you can enhance your overall security posture and streamline troubleshooting processes throughout your cloud-based translation environment.
98+
99+
* **Enable diagnostic logging**: Configure Azure Monitor to collect and analyze logs from your Translator service to identify potential security issues, track usage patterns, and troubleshoot problems.<br>
100+
For more information, *see* [Azure Monitor for Azure AI services](/azure/azure-monitor/platform/monitor-azure-resource).
101+
102+
* **Set up alerts for unusual activity**: Create Azure Monitor alerts to notify you of abnormal usage patterns, potential security breaches, or service disruptions affecting your Translator resources.<br>
103+
For more information, *see* [Create, view, and manage metric alerts using Azure Monitor](/azure/azure-monitor/alerts/alerts-metric).
104+
105+
* **Configure audit logs**: Enable and review audit logs to monitor access and changes to your Translator resources. Audit logs ensure you know who is using your service and what actions are being performed.<br>
106+
For more information, *see* [Resource logs in Azure Monitor](/azure/azure-monitor/platform/resource-logs).
107+
108+
* **Implement request rate monitoring**: Monitor API request rates to detect potential denial of service attacks or unauthorized usage, ensuring your service remains available for legitimate use.<br>
109+
For more information, *see* [Service and request limits for Azure AI Translator](/azure/ai-services/translator/service-limits).
110+
111+
## Compliance and governance
112+
113+
To ensure the secure operation of Azure AI Translator services, you need to put a robust governance framework in place and consistently comply with all relevant standards. By establishing thorough policies and procedures, you can effectively protect your systems, maintain regulatory compliance, and minimize potential risks, ultimately delivering reliable and secure service.
114+
115+
* **Review Azure Policy for AI services**: Implement Azure Policy to enforce organization-wide security standards for your AI services, including network isolation requirements.<br>
116+
For more information, *see* [Azure Policy Regulatory Compliance controls for Azure AI services](/azure/ai-services/security-controls-policy#microsoft-cloud-security-benchmark).
117+
118+
* **Conduct regular security assessments**: Continuously assess the security status of your Translator deployments and ensure they align with industry standards and organizational policies. Promptly detect and address any potential vulnerabilities as they arise.<br>
119+
For more information, *see* [Microsoft cloud security benchmark](/security/benchmark/azure/introduction).
120+
121+
* **Maintain regulatory compliance**: Configure your Translator service to comply with all relevant laws and regulations that apply to your industry and geographic area. Make sure to pay special attention to any requirements related to data privacy and protection.<br>
122+
For more information, *see* [Azure AI Translator Transparency Note](/azure/ai-foundry/responsible-ai/translator/transparency-note).
123+
124+
* **Implement human oversight**: For sensitive translation scenarios, implement a human review workflow to verify translation accuracy. This process ensures that all content complies with organizational standards before wide distribution.<br>
125+
For more information, *see* [Azure AI Translator Transparency Note](/azure/ai-foundry/responsible-ai/translator/transparency-note#evaluating-and-integrating-azure-ai-translator-for-your-use).
126+
127+
128+
129+
130+
## Related content
131+
132+
* [Azure AI Translator documentation](/azure/ai-services/translator/)
133+
* [Microsoft Cloud Security Benchmark – Azure AI services](/security/benchmark/azure/baselines/azure-openai-security-baseline)
134+
* [Well-Architected Framework – AI workloads](/azure/well-architected/ai/design-principles)
135+
* [Security documentation for Azure AI services](/azure/ai-services/security-features)

articles/ai-services/translator/toc.yml

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,9 @@ items:
2727
- name: Translator Service FAQ
2828
displayName: character,count,usage,attribution, cognitive
2929
href: translator-faq.md
30-
31-
30+
- name: Secure deployment guide
31+
displayName: support,plan,issue,problem,bug,troubleshoot,troubleshooting
32+
href: secure-deployment.md
3233

3334
- name: Text translation (GA)
3435
items:

0 commit comments

Comments
 (0)