Requirements:
- User Addition and Authentication:
- Objective: Allow users (Content manager, Sales admin, Placement admin etc) to register and authenticate securely.
- Implementation:
- Multiple domain would be adding a user screen where individuals can be added using their email addresses.
- Password policies are enforced, requiring users to create strong, unique passwords and further it can be done through OTP based authorization for suspicious login.
- IP address and geo-location tracking to detect suspicious login and prevent from hacking
- Enforcing users to reset password after 60 days for prevention of data breach.
- Auto-logout after 7 days or if the user is inactive for 72 hours
2. Role-Based Access Control (RBAC):-
- Objective: Control access to different resources based on users' roles and responsibilities.
- Implementation:
- Applications define various user roles such as Content manager, Sales admin, Placement admin etc.
- Each role is associated with specific permissions and access rights. So the user will be compartmentalised accordingly.
- RBAC ensures that users only have access to the resources necessary for their roles, minimising the risk of unauthorised access.
3. Single Sign-On (SSO):
- Objective: Simplify the login process for users accessing multiple services and platforms in different domain.
- Implementation:
- Implement SSO functionality, allowing users to log in once and access multiple services without needing to re-enter their credentials.
- Integration with popular identity providers such as OpenID base enables seamless authorization across platforms.
- SSO enhances the user experience and reduces the burden of managing multiple login credentials.
4. Access Management and Authorization:
- Objective: Monitor and control access to sensitive data and resources.
- Implementation:
- Access controls are implemented at both the application and data levels to restrict unauthorised access.
- Fine-grained access policies define who can view, edit, or delete specific resources within the platform.
- Regular access reviews and audits are conducted to ensure compliance with security policies and regulations.
5. Identity Lifecycle Management:
- Objective: Manage user identities throughout their lifecycle, from onboarding to offboarding.
- Implementation:
- Automated processes handle user provisioning and deprovisioning based on predefined workflows.
- Upon joining multiple organizations or departments, new employees undergo identity verification and are provisioned with appropriate access rights based on their roles.
- When employees leave the organisation, their access privileges are revoked promptly to prevent unauthorised access.
- Master activity log can be maintained that will help to monitor individual access
6. Security Monitoring and Incident Response:
- Objective: Detect and respond to security threats in real-time.
- Implementation:
- Continuous monitoring of user activities and access logs helps identify suspicious behaviour or unauthorised access attempts.
- An incident response plan outlines procedures for addressing security incidents, including breach detection, containment, and recovery.
- Security alerts and notifications are configured to notify administrators of potential security threats promptly.
Benefits from IAM:
- Enhanced Security: It measures ensure secure access to resources, reducing the risk of data breaches and unauthorised access.
- Improved User Experience: SSO and streamlined authentication processes enhance user convenience and productivity.
- Regulatory Compliance: IAM frameworks may help organizations comply with data protection regulations by enforcing access controls and maintaining audit trails.
Efficient Resource Management: RBAC and automated identity lifecycle management streamline resource allocation and minimise administrative overhead.