Identity Providers & Federation (Part 2)

By Ashwin Venugopal -

 





To read part 1, please click here



Using Web Identity Federation API Operations for Mobile Apps

Using Amazon Cognito as your identity broker offers best results for almost all identity federation scenarios. But, if you have already created an app that can use web identity federation by manually calling the AsumeRoleWithWebIdentity API, you can use it continuously and your apps will be fine. The process for using web identity federation without Amazon Cognito is as follows:
  • Firstly, you have to sign-up as a developer with the external identity provider and configure your apps with the provider. You can also configure multiple apps with each provider.

  • If you use an IdP other than Google, Facebook or Amazon Cognito compatible with OIDC, then create an IAM identity provider entity for it.

  • In IAM, create one or more roles, and define roles and permissions the app's users have, for each role.

  • After that, you have to authenticate your users with the IdP, in your app. However, how to perform this task might vary according to which identity you use and on which platform your app runs.

  • Now, you can make an unsigned call to the AsumeRoleWithWebIdentity action in order to request temporary security credentials. After which, AWS verifies the authenticity of the token and returns temporary security credentials to your app that have the permissions for the role that you name in the request. The response also includes metadata about the user from the IdP, such as the unique user ID that the IdP associates with the user.

  • While using the temporary security credentials from the AsumeRoleWithWebIdentity response, your app makes signed requests to AWS API operations. This allows you to create access control policies that can lock the folder so that only the user with that ID can access it.

  • Your app should also be able cache the temporary security credentials so that you don't have to get the new ones each time the app needs to make a request to AWS. The credentials are good for about one hour by default and when they expires you have to call AssumeRoleWithWebIdentity a new set of temporary security credentials. However, if you use the AWS SDK for iOS or the AWS SDK for Android, you can take help of AmazonStSCredentialsProvider action, that can manage as well as refresh the IAM temporary credentials as required.   







To read part 1, please click here
































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more