<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/require-proof-of-presence-for-high-impact-actions-z6iywei06" -->

---
title: Require proof of presence for high-impact actions
description: GitHub Enterprise Cloud now supports a public preview feature called proof of presence, which requires members to re-authenticate or complete an MFA challenge...
canonical: https://daily.dev/posts/require-proof-of-presence-for-high-impact-actions-z6iywei06
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Require proof of presence for high-impact actions | daily.dev
og:description: GitHub Enterprise Cloud now supports a public preview feature called proof of presence, which requires members to re-authenticate or complete an MFA challenge...
og:url: https://daily.dev/posts/require-proof-of-presence-for-high-impact-actions-z6iywei06
og:image: https://api.daily.dev/og/posts/Z6iYWeI06.png
og:image:alt: Require proof of presence for high-impact actions
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Require proof of presence for high-impact actions

**[GitHub Changelog](https://daily.dev/sources/github_updates)** · 3 min read · 0 upvotes · 0 comments

## Summary

GitHub Enterprise Cloud now supports a public preview feature called proof of presence, which requires members to re-authenticate or complete an MFA challenge via their identity provider before performing high-impact actions such as creating tokens, editing webhooks, or changing security settings. It extends GitHub's existing sudo mode and is currently limited to managed user (EMU) enterprises on github.com and GHEC-DR using Microsoft Entra ID as their SSO IdP via SAML or OIDC. The feature aims to counter stolen session cookies and long-lived token abuse seen in recent supply chain attacks, and helps meet compliance frameworks like FDA Part 11. After a successful check, users get a two-hour grace period before needing to re-verify. Support for requiring proof of presence before pull request merges is planned.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://github.blog/changelog/2026-09-24-require-proof-of-presence-for-high-impact-actions>

## Questions this post answers

### What is proof of presence in GitHub Enterprise Cloud?

Proof of presence is a public preview feature that requires an interactive re-authentication or multi-factor challenge before members can take high-impact actions like creating tokens, editing webhooks, or changing organization security settings. It extends GitHub's sudo mode by redirecting the user to their identity provider to confirm a real authorized person is acting, not just a valid session or token, blocking compromised credentials from being used.

_admins hardening GitHub enterprise security can track features like this via daily.dev._

### Which identity providers support GitHub's proof of presence feature?

Proof of presence in public preview is scoped only to managed user (EMU) enterprises on github.com and GHEC-DR that use Microsoft Entra ID as their SSO identity provider, connected via SAML or OIDC. Configuration options include requiring re-authentication or an additional MFA challenge, with policies set through Entra ID.

_teams evaluating SSO-based security hardening can follow GitHub changes on daily.dev._

### How long does a GitHub proof of presence check last before requiring another challenge?

After a successful proof of presence challenge, a user can continue performing high-impact actions in that same browser session for two hours without needing to repeat the check. This mirrors the session model already used by GitHub's sudo mode.

_security-conscious admins tuning session policies can keep tabs on GitHub updates via daily.dev._

## Similar posts on daily.dev

- [Public monitoring now available with data residency](https://daily.dev/posts/public-monitoring-now-available-with-data-residency-4fwlra79o) · GitHub Changelog · 0 upvotes · 0 comments
- [GitHub ships break glass credential revocation](https://daily.dev/posts/github-ships-break-glass-credential-revocation-cii7k9djr) · Aikido Security · 0 upvotes · 0 comments
- [Enterprise-wide credential management tools for incident response](https://daily.dev/posts/enterprise-wide-credential-management-tools-for-incident-response-o4y8yihch) · GitHub Changelog · 0 upvotes · 0 comments
- [Strengthening GitLab.com security: Mandatory MFA](https://daily.dev/posts/strengthening-gitlab-com-security-mandatory-mfa-5dcymzi9j) · GitLab · 1 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#github](https://daily.dev/tags/github), [#authentication](https://daily.dev/tags/authentication)

[View this post on daily.dev](https://daily.dev/posts/require-proof-of-presence-for-high-impact-actions-z6iywei06)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Require proof of presence for high-impact actions","url":"https://daily.dev/posts/require-proof-of-presence-for-high-impact-actions-z6iywei06","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/require-proof-of-presence-for-high-impact-actions-z6iywei06"},"datePublished":"2026-09-24T20:55:25.711Z","dateModified":"2026-09-24T20:55:46.302Z","description":"GitHub Enterprise Cloud now supports a public preview feature called proof of presence, which requires members to re-authenticate or complete an MFA challenge...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f6495077f11e7c71c1c0e4d308b08a49?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f6495077f11e7c71c1c0e4d308b08a49?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Changelog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Changelog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/15004b7835da4d89b02b115871f0f6dc","url":"https://daily.dev/sources/github_updates"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/require-proof-of-presence-for-high-impact-actions-z6iywei06","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,github,authentication","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Changelog","item":"https://daily.dev/sources/github_updates"},{"@type":"ListItem","position":3,"name":"Require proof of presence for high-impact actions"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/require-proof-of-presence-for-high-impact-actions-z6iywei06#faq","mainEntity":[{"@type":"Question","name":"What is proof of presence in GitHub Enterprise Cloud?","acceptedAnswer":{"@type":"Answer","text":"Proof of presence is a public preview feature that requires an interactive re-authentication or multi-factor challenge before members can take high-impact actions like creating tokens, editing webhooks, or changing organization security settings. It extends GitHub's sudo mode by redirecting the user to their identity provider to confirm a real authorized person is acting, not just a valid session or token, blocking compromised credentials from being used. admins hardening GitHub enterprise security can track features like this via daily.dev."}},{"@type":"Question","name":"Which identity providers support GitHub's proof of presence feature?","acceptedAnswer":{"@type":"Answer","text":"Proof of presence in public preview is scoped only to managed user (EMU) enterprises on github.com and GHEC-DR that use Microsoft Entra ID as their SSO identity provider, connected via SAML or OIDC. Configuration options include requiring re-authentication or an additional MFA challenge, with policies set through Entra ID. teams evaluating SSO-based security hardening can follow GitHub changes on daily.dev."}},{"@type":"Question","name":"How long does a GitHub proof of presence check last before requiring another challenge?","acceptedAnswer":{"@type":"Answer","text":"After a successful proof of presence challenge, a user can continue performing high-impact actions in that same browser session for two hours without needing to repeat the check. This mirrors the session model already used by GitHub's sudo mode. security-conscious admins tuning session policies can keep tabs on GitHub updates via daily.dev."}}]}
```

