Most organizations have security as a primary concern for their cloud environment. Users want to make sure that their cloud infrastructure is secure enough so that they deploy their maximum resources on the cloud without worrying about its safety. Centilytics ensures that your cloud infrastructure attains maximum security and recommends some practices related to AWS EBS snapshot in order to help you achieve maximum security for your data stored in EBS volumes.
What is an AWS EBS snapshot?
EBS is a block storage service provided by AWS which is used to store persistent data. Amazon EBS is suitable for EC2 instances by providing block-level storage volumes. There are mainly three varieties of volumes – General Purpose (SSD), Provisioned IOPS (SSD), and Magnetic which differ in performance, characteristics, and cost. AWS gives the provision of creating multiple snapshots of these volumes. A Snapshot is basically an incremental backup created for the data stored in EBS volumes
How do EBS snapshots work?
EBS snapshots are stored in AWS S3 buckets. Only unique blocks of EBS volume data that has changed since the last stored EBS snapshot are saved in the next EBS snapshot.
Why public EBS snapshots are a major threat to your cloud security?
It is recommended that the EBS snapshots should not be public. Public AWS EBS snapshot means that data which is backed up in that particular snapshot is accessible to all other AWS accounts. This means the other person can not only access and copy your data but can also create a volume out of it. This can lead to the misuse of your sensitive data. There might be a situation where you can have numerous snapshots created in your cloud infrastructure and you might not be aware of any public snapshot which may contain any sensitive information which is not supposed to be shared.
Centilytics comes into play
This is where our cloud management platform comes to your rescue. Centilytics lists down all the public snapshots available in your cloud infrastructure, allowing you to analyze and act against them from your AWS console.
|CRITICAL||If a snapshot is marked public then it will be displayed in this insight.|
Description of further columns are as follows:
- Account Id: Shows the respective account ID of the user’s account.
- Account Name: Shows corresponding account name to the user’s account.
- Region: Shows the region in which the corresponding snapshot exists.
- Identifier: Shows the unique snapshot Id of the snapshot.
- Description: Shows the description of the snapshot given by the user.
|Compliance Name||Reference No.||Link|
|Account Id||Applying this filter will display all the public snapshots for the selected account Id.|
|Region||Applying the region filter will display all the public snapshots corresponding to the selected region.|
|Severity||Applying severity filter will display public snapshots according to the selected severity type i.e. selecting critical will display all instances with critical severity. Same will be the case for Warning and Ok severity types.|
|Resource Tags||Applying resource tags filter will display those public snapshots which have been assigned the selected resource tag. For eg- If the user has tagged some public snapshots by a resource tag named environment, then selecting an environment from the resource tags filter will display all those snapshots.|
|Resource Tags Value||Applying resource tags value filter will display data which will have the selected resource tag value. For e.g. – Let’s say a user has tagged some resource by a tag named environment and has a value say production (environment:production). Hence, the user can view data of all the resources which have “environment:production” tag assigned. The user can use the tag value filter only when a tag name has been provided.|