Account/Authentication - Azure Active Directory - Ensure the Option to Remain Signed-in is Hidden

By Ashwin Venugopal -

 







Summary

The option Stay signed in or Keep me signed in will be prompted after a successful login, and when a user select this option, a persistent refresh token is created which will generally last till 90 days and does not prompt for sign-in or Multi-Factor.

Reason

If the users are permitted to choose this option, it may pose risk especially when the user signs into their account on a publicly accessible computer/web browser. This will result in easier access for an unauthorized person to any associated cloud data from that account.

What If?

Hiding this setting, will result in no Stay signed in? message prompts during signing-in, which also means that users will be forced to sign-in more frequently.

Note- Some of the SharePoint Online and Office 2012 features have a dependency on users remaining signed in. If this option id hidden, then, users may get additional and unexpected sign-in prompts.

How to?

To verify the option to remain signed-in is disabled, use the Microsoft 365 Admin Center:
  1. Login to https://admin.microsoft.com as a Global Administrator.
  2. Go to Admin centers then choose Azure Active Directory.
  3. Now, under Manage select Company branding followed by the appropriate Locale policy.
  • If no policy exists, then, you have to click Configure to create one.
      4. After that, scroll to the bottom of the newly opened pane and ensure Show option to remain                    signed-in is not checked.
      5. Click Save.

Monitor:

To verify the option to remain signed-in is disabled, use the Microsoft 365 Admin Center:
  1. Login to https://admin.microsoft.com as a Global Administrator.
  2. Go to Admin centers then choose Azure Active Directory.
  3. Now, under Manage select Company branding followed by the appropriate Locale policy.
  • If you see Configure then no locale or policy exists and this setting is not applied, proceed to remediation.

      4. After that, scroll to the bottom of the newly opened pane and ensure Show option to remain                    signed-in is not checked.







































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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more