Quick Start Security for Azure Blob Storage
Thank you!
We got your information.
Coralogix Extension For Azure Blob Storage Includes:
Alerts - 5
Stay on top of Azure Blob Storage key performance metrics. Keep everyone in the know with integration with Slack, PagerDuty and more.
Azure Blob - Azure Blob Storage Encryption at Rest
This use case focuses on implementing encryption at rest for Azure Blob Storage to safeguard data from unauthorized access. Encryption at rest ensures that even if physical storage media or files are compromised, the data remains secure through encryption. Impact Data Encryption Protect sensitive data by encrypting it at rest, mitigating the risk of unauthorized access to stored information. Compliance Fulfill compliance requirements that mandate the use of encryption to protect sensitive data. Mitigation Enable SSE Enable Storage Service Encryption for the Azure Blob Storage account to encrypt data at rest. Choose Key Management Option Select the appropriate key management option, either using Microsoft-managed keys or customer-managed keys, based on organizational security policies. Regular Key Rotation Implement regular key rotation practices to enhance the security of the encryption keys. Mitre tactic: TA0005 Mitre technique: T1022
Azure Blob - Anonymous Access/Configuration Changes to Blob Containers
This use case involves monitoring and auditing for instances where anonymous access is granted or configuration changes are made to Azure Blob Containers. Anonymous access or unauthorized configuration changes can pose significant security risks to the stored data. Impact Data Exposure: Unauthorized anonymous access can expose sensitive data to the public or unauthorized users. Data Integrity: Configuration changes may lead to unintended exposure, modification, or deletion of data. Regulatory Compliance: Violations of data access controls may lead to non-compliance with regulatory requirements. Mitigation Role-Based Access Control (RBAC): Implement RBAC to ensure that only authorized users have the necessary permissions to modify container configurations. Azure AD Authentication: Enforce Azure Active Directory authentication to restrict access and prevent anonymous access. Mitre tactic: TA0040 Mitre technique : T1583
Azure Blob - Disallow Public Access to Blob in Storage Accounts
This use case involves configuring Azure Storage Accounts to disallow public access to blobs. Public access to blobs in storage accounts can pose security risks by exposing sensitive data to unauthorized users. This use case focuses on preventing such public access to enhance data security. Impact Data Security: Disallowing public access ensures that sensitive data stored in Azure Storage Blobs is not exposed to unauthorized users or the public. Compliance: Enforcing access restrictions aligns with regulatory requirements and industry best practices, contributing to compliance with data protection standards. Mitigation Azure Storage Account Configuration: Adjust the configuration settings of the Azure Storage Account to ensure that public access to blobs is disallowed. Shared Access Signatures (SAS): Implement Shared Access Signatures for controlled and temporary access to blobs, allowing fine-grained control over permissions. Azure AD Authentication: Leverage Azure Active Directory (Azure AD) authentication mechanisms to control and restrict access to blobs based on user authentication. Mitre tactic: TA0040 Mitre technique: T1530
Azure Blob - Azure Blob Storage account Create/Modify
This use case involves monitoring and auditing activities related to the creation/modification of account within Azure Blob Storage. Azure Blob Storage is a scalable object storage solution that organizations use to store and manage unstructured data. This use case for account creation/modification provides a detailed record of activities, including who performed the action, what data was affected, and when the action occurred. Impact Unauthorized access to create/modify account can have significant consequences, including loss of critical information, compliance violations, and potential business disruption. Understanding the impact involves recognizing the potential for data breaches, data loss, or compromised integrity, leading to legal and financial repercussions. Mitigation Implement Role-Based Access Control (RBAC): Assign appropriate roles and permissions to users and applications accessing Azure Blob Storage. Limit access to only those individuals or services that require it, reducing the risk of unauthorized modifications. Regularly Review Audit Logs: Periodically review and analyze the audit logs for data deletion/modification events. This proactive approach helps identify anomalies, potential security incidents, or unauthorized activities promptly. Implement Soft Delete: Enable soft delete for Azure Blob Storage containers, allowing the recovery of deleted data within a specified retention period. This acts as a safety net in case of accidental deletions. Use Azure Policy and Azure Security Center Mitre tactic: TA0040 Mitre technique: T1530
Azure Blob - Azure Blob Storage Data Deletion
This use case involves monitoring and auditing activities related to the deletion of data within Azure Blob Storage. Azure Blob Storage is a scalable object storage solution that organizations use to store and manage unstructured data. This use case for data deletion provides a detailed record of activities, including who performed the action, what data was affected, and when the action occurred. Impact Unauthorized or accidental deletion of data can have significant consequences, including loss of critical information, compliance violations, and potential business disruption. Understanding the impact involves recognizing the potential for data breaches, data loss, or compromised integrity, leading to legal and financial repercussions. Mitigation Implement Role-Based Access Control (RBAC): Assign appropriate roles and permissions to users and applications accessing Azure Blob Storage. Limit access to only those individuals or services that require it, reducing the risk of unauthorized modifications. Regularly Review Audit Logs: Periodically review and analyze the audit logs for data deletion/modification events. This proactive approach helps identify anomalies, potential security incidents, or unauthorized activities promptly. Implement Soft Delete: Enable soft delete for Azure Blob Storage containers, allowing the recovery of deleted data within a specified retention period. This acts as a safety net in case of accidental deletions. Use Azure Policy and Azure Security Center Mitre tactic: TA0040 Mitre technique: T1530
Integration
Learn more about Coralogix's out-of-the-box integration with Azure Blob Storage in our documentation.