In Week 1, you discussed GIG, Inc.’s benefits and concerns with moving to the cloud. In Week 2, you created a high-level diagram of a system using built-in AWS that provided reliability, availability, and continuity across the migrated environment. Last week, you chose a database and created a diagram that visualized the chosen system and implementation steps.

QUESTION

In Week 1, you discussed GIG, Inc.’s benefits and concerns with moving to the cloud. In Week 2, you created a high-level diagram of a system using built-in AWS that provided reliability, availability, and continuity across the migrated environment. Last week, you chose a database and created a diagram that visualized the chosen system and implementation steps.

This week, you will create a Microsoft® Excel® spreadsheet and provide a summary for the critical IAM structure provided below. This will be used for all systems and ensure all users have only the privileges needed for their job.

The company has three levels of access:

• Customer (Minimal-web only)
• Administrative (Implementation-access to Cloud environment at a programmatic level and operational level)
• System (The requirement(s) for system to system access)

The company security compliance controls need to ensure that each level of access is only allowed to authorized users/systems.

Create a Microsoft® Excel® spreadsheet matrix listing all applicable information for each level of access, and ensure you include this information:

• AWS that provide access control (network access control list, domain name service, security groups, etc.)
• Types of restrictions (port, protocols, etc.)
• The specific implementation matrix for each level (security groups will only allow port 22 to this level)
• A basic set of IAM users, groups, and roles

Write a 1-page summary in Microsoft® Word about the structures and security benefits.

Submit your spreadsheet and summary.

ANSWER

 IAM Structure and Security Benefits for GIG, Inc.’s Cloud Migration

Introduction

As GIG, Inc. transitions its systems to the cloud, ensuring robust access control and security measures is crucial to safeguarding sensitive information and maintaining operational efficiency. This document presents the IAM (Identity and Access Management) structure for GIG, Inc.’s cloud environment, along with a comprehensive matrix outlining access control mechanisms and restrictions. The IAM structure encompasses three levels of access: Customer, Administrative, and System. By implementing this IAM structure, GIG, Inc. can enforce fine-grained access privileges, mitigate security risks, and streamline operations.

IAM Structure Overview

Customer Level Access

   – AWS Access Control: Web-only access via AWS Identity and Access Management (IAM) users and groups.

   – Restrictions: Limited to web-based functionalities, ensuring minimal privileges required for customer interaction.

   – Implementation Matrix: IAM policy limits access to specific web-based services and resources relevant to customers.

Administrative Level Access

   – AWS Access Control: Programmatic and operational access to the cloud environment using IAM roles and policies.

   – Restrictions: Access restrictions imposed at multiple levels, such as network access control lists (NACLs) and security groups (Control Traffic to Subnets Using Network ACLs – Amazon Virtual Private Cloud, n.d.).

   – Implementation Matrix: IAM roles with necessary policies and permissions to enable administrative tasks, following the principle of least privilege.

System Level Access

   – AWS Access Control: Facilitates secure communication and integration between systems.

   – Restrictions: Granular restrictions implemented at the network level, leveraging security groups, NACLs, and other mechanisms.

   – Implementation Matrix: IAM roles with specialized permissions to allow seamless system-to-system communication, adhering to predefined protocols and ports.

IAM Users, Groups, and Roles:

To effectively manage access control across GIG, Inc.’s cloud environment, the following IAM entities are established:

 IAM Users

   – These entities represent individual users and are associated with unique credentials.

   – IAM users are grouped based on their roles, which helps in managing permissions effectively (Kalagara, 2022).

IAM Groups

   – Groups are logical collections of IAM users with similar job roles or responsibilities.

   – IAM policies are attached to groups, simplifying permissions management for multiple users simultaneously.

IAM Roles

   – Roles are assigned to IAM users and provide a temporary set of permissions.

   – IAM roles follow the principle of least privilege, granting users only the necessary permissions required to fulfill their duties.

Summary of IAM Structure and Security Benefits:

Implementing the IAM structure outlined above offers several key security benefits for GIG, Inc.’s cloud environment:

 Fine-Grained Access Control: The IAM structure ensures that each user or system has precisely the privileges required for their job responsibilities, minimizing the risk of unauthorized access.

Principle of Least Privilege: By adhering to the principle of least privilege, IAM roles and policies grant users and systems only the necessary permissions, reducing the attack surface and potential impact of security breaches.

Access Control Mechanisms: Utilizing AWS-native access control mechanisms such as security groups, NACLs, and IAM policies enables the implementation of granular restrictions at the network level, ensuring secure communication and data protection.

Simplified Management: IAM users, groups, and roles provide a centralized approach to access control management, allowing efficient assignment and revocation of permissions, ensuring compliance, and simplifying auditing processes (Security Best Practices in IAM – AWS Identity and Access Management, n.d.).

Compliance and Regulatory Alignment: The IAM structure facilitates the enforcement of security compliance controls, ensuring that access is limited to authorized users and systems. This helps meet regulatory requirements and industry best practices.

Conclusion

The IAM structure implemented for GIG, Inc.’s cloud environment ensures effective access control, security, and compliance throughout the migration process. By leveraging AWS’s robust access control mechanisms and following the principle of least privilege, GIG, Inc. can safeguard sensitive data, streamline operations, and minimize the risk of security breaches. This comprehensive IAM structure provides a solid foundation for the company’s cloud-based systems, promoting secure and efficient operations in the digital landscape.

References

Control traffic to subnets using network ACLs – Amazon Virtual Private Cloud. (n.d.). https://docs.aws.amazon.com/vpc/latest/userguide/vpc-network-acls.html 

Kalagara, S. (2022, September 30). What is AWS Identity and Access Management? What is AWS Identity and Access Management? https://www.veritis.com/blog/what-is-aws-identity-and-access-management/ 

Security best practices in IAM – AWS Identity and Access Management. (n.d.). https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html