Observium running in Ubuntu Server / How to ensure data at REST encrypted with AES256 / data encryption at rest
Hi ,
Subject - Data encryption at REST ( AES256 )
How to verify and ensure data at REST encrypted with AES256 Observium running in Ubuntu Server.
When at rest, data can be subject to malicious threats such as data theft or data corruption by obtaining physical access to the storage hardware.
Do share us information if any comments for this.
Thank you
Regards Ryan
**************************************** There are three states for digital data: data in use, data in transit and data at rest.
* Data in use refers to active data stored in non-persistent volumes, typically RAM or CPU caches.
* Data in transit is the state where data is transferred over a network, either private or public.
* Data at rest means inactive data that is stored physically on persistent storage, i.e. disks, databases, data warehouses, mobile devices, archives, etc.
Hi Ryan,
These are really questions for your system administration team, and not related to Observium.
But in short: - Use self encrypting drives and configure them with a passphrase, or - Use the drive encryption feature of your RAID controller, or - Use LUKS on your Linux Host OS to encrypt the LVM volumes that contain Observium or its VM
Tom
On 2022-04-14 08:47, Ryan Tee via observium wrote:
Hi ,
Subject – *_Data encryption at REST ( AES256 )_*
How to verify and ensure data at REST encrypted with AES256 Observium running in Ubuntu Server.
When at rest, data can be subject to malicious threats such as data theft or data corruption by obtaining physical access to the storage hardware.
Do share us information if any comments for this.
Thank you
Regards
Ryan
There are three states for digital data: data in use, data in transit and data at rest.
·Data in use refers to active data stored in non-persistent volumes, typically RAM or CPU caches.
·Data in transit is the state where data is transferred over a network, either private or public.
·Data at rest means inactive data that is stored physically on persistent storage, i.e. disks, databases, data warehouses, mobile devices, archives, etc.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Tom,
Thanks for reply ad information.
We will check with systems team.
Regards Ryan
From: observium observium-bounces@observium.org On Behalf Of Tom Laermans via observium Sent: Friday, 15 April 2022 12:14 am To: observium@observium.org Cc: Tom Laermans tom.laermans@powersource.cx Subject: Re: [Observium] Observium running in Ubuntu Server / How to ensure data at REST encrypted with AES256 / data encryption at rest
Hi Ryan,
These are really questions for your system administration team, and not related to Observium.
But in short: - Use self encrypting drives and configure them with a passphrase, or - Use the drive encryption feature of your RAID controller, or - Use LUKS on your Linux Host OS to encrypt the LVM volumes that contain Observium or its VM
Tom
On 2022-04-14 08:47, Ryan Tee via observium wrote: Hi ,
Subject – Data encryption at REST ( AES256 )
How to verify and ensure data at REST encrypted with AES256 Observium running in Ubuntu Server.
When at rest, data can be subject to malicious threats such as data theft or data corruption by obtaining physical access to the storage hardware.
Do share us information if any comments for this.
Thank you
Regards Ryan
**************************************** There are three states for digital data: data in use, data in transit and data at rest.
1. Data in use refers to active data stored in non-persistent volumes, typically RAM or CPU caches.
2. Data in transit is the state where data is transferred over a network, either private or public.
3. Data at rest means inactive data that is stored physically on persistent storage, i.e. disks, databases, data warehouses, mobile devices, archives, etc.
_______________________________________________
observium mailing list
observium@observium.orgmailto:observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (2)
-
Ryan Tee -
Tom Laermans