AWS iot-device-defender documentation change
Summary
Removed mention of default inability to perform tasks via AWS Management Console/CLI/API from policy explanation
Security assessment
The change simplifies the description of default permissions but does not address a specific security vulnerability or weakness. It removes redundant information about access methods (console/CLI/API) while maintaining the core security principle of least privilege through IAM policies.
Diff
diff --git a/iot-device-defender/latest/devguide/security_iam_id-based-policy-examples.md b/iot-device-defender/latest/devguide/security_iam_id-based-policy-examples.md index 0f2af1e99..116484f39 100644 --- a//iot-device-defender/latest/devguide/security_iam_id-based-policy-examples.md +++ b//iot-device-defender/latest/devguide/security_iam_id-based-policy-examples.md @@ -9 +9 @@ Policy best practicesUsing the consoleAllow users to view their own permissions -By default, users and roles don't have permission to create or modify AWS IoT Device Defender resources. They also can't perform tasks by using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles. +By default, users and roles don't have permission to create or modify AWS IoT Device Defender resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.