AWS iot-mi documentation change
Summary
Updated capitalization of 'managed integrations' to 'Managed Integrations' throughout the document for consistency
Security assessment
Changes are purely cosmetic capitalization adjustments with no modifications to security content, encryption mechanisms, or vulnerability disclosures. The security practices described remain identical.
Diff
diff --git a/iot-mi/latest/devguide/data-protection.md b/iot-mi/latest/devguide/data-protection.md index 76d98881c..a3670c306 100644 --- a//iot-mi/latest/devguide/data-protection.md +++ b//iot-mi/latest/devguide/data-protection.md @@ -7 +7 @@ -Data encryption at rest for managed integrations +Data encryption at rest for Managed Integrations @@ -9 +9 @@ Data encryption at rest for managed integrations -# Data protection in managed integrations +# Data protection in Managed Integrations @@ -11 +11 @@ Data encryption at rest for managed integrations -The AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) applies to data protection in Managed integrations for AWS IoT Device Management. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see [Data Privacy FAQ](https://aws.amazon.com/compliance/data-privacy-faq/). For information about data protection in Europe, see the [General Data Protection Regulation (GDPR) Center](https://aws.amazon.com/compliance/gdpr-center/). +The AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) applies to data protection in Managed Integrations for AWS IoT Device Management. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see [Data Privacy FAQ](https://aws.amazon.com/compliance/data-privacy-faq/). For information about data protection in Europe, see the [General Data Protection Regulation (GDPR) Center](https://aws.amazon.com/compliance/gdpr-center/). @@ -32 +32 @@ We strongly recommend that you never put confidential or sensitive information, -## Data encryption at rest for managed integrations +## Data encryption at rest for Managed Integrations @@ -34 +34 @@ We strongly recommend that you never put confidential or sensitive information, -Managed integrations for AWS IoT Device Management encrypts sensitive customer data at rest by default using encryption keys. +Managed Integrations for AWS IoT Device Management encrypts sensitive customer data at rest by default using encryption keys. @@ -36 +36 @@ Managed integrations for AWS IoT Device Management encrypts sensitive customer d -There are two types of encryption keys that are used to protect sensitive data for managed integrations customers: +There are two types of encryption keys that are used to protect sensitive data for Managed Integrations customers: @@ -40 +40 @@ There are two types of encryption keys that are used to protect sensitive data f -Managed integrations supports the use of symmetric customer managed key that you can create, own, and manage. You have full control over these KMS keys, including establishing and maintaining their key policies, IAM policies, and grants, enabling and disabling them, rotating their cryptographic material, adding tags, creating aliases that refer to the KMS keys, and scheduling the KMS keys for deletion. +Managed Integrations supports the use of symmetric customer managed key that you can create, own, and manage. You have full control over these KMS keys, including establishing and maintaining their key policies, IAM policies, and grants, enabling and disabling them, rotating their cryptographic material, adding tags, creating aliases that refer to the KMS keys, and scheduling the KMS keys for deletion. @@ -44 +44 @@ Managed integrations supports the use of symmetric customer managed key that you -Managed integrations uses these keys by default to automatically encrypt sensitive customer data. You can't view, manage, or audit their use. You don't have to take any action or change any programs to protect the keys that encrypt your data. Encryption of data at rest by default helps reduce the operational overhead and complexity involved in protecting sensitive data. At the same time, it enables you to build secure applications that meet strict encryption compliance and regulatory requirements. +Managed Integrations uses these keys by default to automatically encrypt sensitive customer data. You can't view, manage, or audit their use. You don't have to take any action or change any programs to protect the keys that encrypt your data. Encryption of data at rest by default helps reduce the operational overhead and complexity involved in protecting sensitive data. At the same time, it enables you to build secure applications that meet strict encryption compliance and regulatory requirements. @@ -50 +50 @@ For more information on the types of AWS KMS encryption keys, see [AWS KMS keys] -### AWS KMS usage for managed integrations +### AWS KMS usage for Managed Integrations @@ -52 +52 @@ For more information on the types of AWS KMS encryption keys, see [AWS KMS keys] -Managed integrations encrypts and decrypts all customer data using envelope encryption. This type of encryption will take your plaintext data and encrypt it with a data key. Next, an encryption key called a wrapping key will encrypt the original data key used to encrypt your plaintext data. In envelope encryption, additional wrapping keys can be used to encrypt existing wrapping keys that are closer in degrees of separation from the original data key. Since the original data key is encrypted by a wrapping key stored separately, you can store the original data key and encrypted plaintext data in the same location. A keyring is used to generate, encrypt, and decrypt data keys in addition to which wrapping key is used to encrypt and decrypt the data key. +Managed Integrations encrypts and decrypts all customer data using envelope encryption. This type of encryption will take your plaintext data and encrypt it with a data key. Next, an encryption key called a wrapping key will encrypt the original data key used to encrypt your plaintext data. In envelope encryption, additional wrapping keys can be used to encrypt existing wrapping keys that are closer in degrees of separation from the original data key. Since the original data key is encrypted by a wrapping key stored separately, you can store the original data key and encrypted plaintext data in the same location. A keyring is used to generate, encrypt, and decrypt data keys in addition to which wrapping key is used to encrypt and decrypt the data key. @@ -60 +60 @@ For more information on envelope encryption, data keys, wrapping keys, and keyri -Managed integrations requires the services to use your customer managed key for the following internal operations: +Managed Integrations requires the services to use your customer managed key for the following internal operations: @@ -75 +75 @@ Managed integrations requires the services to use your customer managed key for -Managed integrations uses encryption keys to encrypt multiple types of data stored at rest. The following list outlines types of data encrypted at rest using encryption keys: +Managed Integrations uses encryption keys to encrypt multiple types of data stored at rest. The following list outlines types of data encrypted at rest using encryption keys: @@ -81 +81 @@ Managed integrations uses encryption keys to encrypt multiple types of data stor - * Managed integrations notifications on various aspects of your device implementation. For more information on managed integrations notifications, see [Set up managed integrations notifications](./managedintegrations-notifications.html#managedintegrations-notification-setup). + * Managed Integrations notifications on various aspects of your device implementation. For more information on Managed Integrations notifications, see [Set up Managed Integrations notifications](./managedintegrations-notifications.html#managedintegrations-notification-setup). @@ -88 +88 @@ Managed integrations uses encryption keys to encrypt multiple types of data stor -### How managed integrations uses key policies in AWS KMS +### How Managed Integrations uses key policies in AWS KMS @@ -90 +90 @@ Managed integrations uses encryption keys to encrypt multiple types of data stor -For branch key rotation and asynchronous calls, managed integrations requires a key policy to use your encryption key. A key policy is used for the following reasons: +For branch key rotation and asynchronous calls, Managed Integrations requires a key policy to use your encryption key. A key policy is used for the following reasons: @@ -97 +97 @@ For branch key rotation and asynchronous calls, managed integrations requires a -For an example of a key policy used to manage access to your encryption key in managed integrations, see Create an encryption key +For an example of a key policy used to manage access to your encryption key in Managed Integrations, see Create an encryption key @@ -101 +101 @@ For an example of a key policy used to manage access to your encryption key in m -For an AWS owned key, a key policy is not required as the AWS owned key is owned by AWS and you can't view, manage, or use it. Managed integrations uses the AWS owned key by default to automatically encrypt your sensitive customer data. +For an AWS owned key, a key policy is not required as the AWS owned key is owned by AWS and you can't view, manage, or use it. Managed Integrations uses the AWS owned key by default to automatically encrypt your sensitive customer data. @@ -103 +103 @@ For an AWS owned key, a key policy is not required as the AWS owned key is owned -In addition to using key policies for managing your encryption configuration with AWS KMS keys, managed integrations uses IAM policies. For more information on IAM policies, see [Policies and permissions in AWS Identity and Access Management.](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) +In addition to using key policies for managing your encryption configuration with AWS KMS keys, Managed Integrations uses IAM policies. For more information on IAM policies, see [Policies and permissions in AWS Identity and Access Management.](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) @@ -117 +117 @@ A key policy statement controls access to an AWS KMS key. Each AWS KMS key will -The following is an example of a key policy statement you can use for managing access and usage to AWS KMS keys stored in your AWS account for managed integrations: +The following is an example of a key policy statement you can use for managing access and usage to AWS KMS keys stored in your AWS account for Managed Integrations: @@ -213 +213 @@ For more information on key stores, see [Key stores](https://docs.aws.amazon.com -The ability to seamlessly update your encryption configuration is critical to managing your data encryption implementation for managed integrations. When you initially onboard with managed integrations, you will be prompted to select your encryption configuration. Your options will be either the default AWS owned keys or create your own AWS KMS key. +The ability to seamlessly update your encryption configuration is critical to managing your data encryption implementation for Managed Integrations. When you initially onboard with Managed Integrations, you will be prompted to select your encryption configuration. Your options will be either the default AWS owned keys or create your own AWS KMS key. @@ -221 +221 @@ To update your encryption configuration in the AWS Management Console, open the -There are two APIs used for managing your encryption configuration of AWS KMS keys in managed integrations: `PutDefaultEncryptionConfiuration` and `GetDefaultEncryptionConfiguration`. +There are two APIs used for managing your encryption configuration of AWS KMS keys in Managed Integrations: `PutDefaultEncryptionConfiuration` and `GetDefaultEncryptionConfiguration`.