> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/whats-new/previous-releases/1.15-to-1.43/version-1.26.md). # Version 1.26 Material Security v1.26 Shut down risky sessions. Triage phishing faster. This release makes it easier than ever to stop compromised accounts in their tracks with new Microsoft 365 session revocation—both automatic and manual. It also delivers major upgrades to phishing issue views and list triage, with better context, cleaner workflows, and richer detections across email, files, and apps. *** ## 🔐 Microsoft 365 Session Revocation Session revocation is now integrated across Material’s detections, letting you stop active threats in real time—automatically or on demand. Auto-remediation now ends M365 sessions when detections trigger—covering threats like: * Accessing multiple sensitive files in quick succession * Sign-ins from known malicious IPs * Activity inconsistent with past behavior * Use of compromised SAML tokens * And more Manual session revocation is now available: * Directly from the Issue details or Account page * Instantly accessible via CMD+K or with a single click *** 🎣 Phishing Issues: More Context, Less Clicks Get to the root of phishing threats faster, with less digging and more immediate insight. * Issues are now generated from phishing cases—just like other detection types * Representative message previews shown by default * Quick links to search messages from the sender or recipient * Tooltips clarify what’s “detected” vs. “similar” * Response actions now follow the same workflow used across the platform * Phishing list view redesigned for scanability and efficient triage * In-issue remediation now feels consistent across all detection types *** ## 🧠 Detection Highlights Smarter detection signals across phishing, files, and apps. Email Detections * Spoofed payment/document messages using Microsoft subdomain links * Long/random sender usernames linked to known phishing campaigns * VIP name in subject, mismatched email + free provider * Known BEC campaign patterns * Sextortion/extortion from first-time senders * Attachments abusing open redirects * Phishing via Slab links File Detections * Investor communications (PPMs, subscription agreements, LP notices) flagged via keyword match App Detections * Social login OAuth grants now excluded from detection scope *** ## ✅ Streamlined File Remediation Configuration Experience * New global setting to enable/disable file remediation across file issues *** v1.26 puts control in your hands and insight at your fingertips—revoking risk and revealing threats with greater clarity and speed.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.material.security/whats-new/previous-releases/1.15-to-1.43/version-1.26.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.