We explain how attackers keep reading mail after M365 session revocation
Comments on “We explain how attackers keep reading mail after M365 session revocation”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
A security research post explains why, after a phished Microsoft 365 user's sessions are revoked or password reset, attackers can keep reading mail through API-based access until existing tokens expire (up to about 90 minutes for access tokens).
Why it ranked
No. 36 of 127 with a score of 0.67. The panel rated it highest on new information (0.89) and practical relevance (0.78), lowest on audience breadth (0.57). Placed No. 36, No. 27 by score alone: the 17th Security story of the day (−0.080). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Practical, technically detailed security analysis of how M365 session revocation fails to block Graph/EWS/ActiveSync access; directly actionable for defenders and IT, with a clear comparison table, though it is narrower in audience.
- AI judgeJudge 3gpt-5.6-luna
- A technically detailed, actionable analysis of Microsoft 365 token-revocation behavior, showing that API access can persist after common remediation and specifying when account disabling is necessary.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.67total under rubric v2.3
- Significance0.58
- Reader interest0.77
- Audience breadth0.57
- Practical relevance0.78
- Substantiated0.61
- Technical depth0.76
- New information0.89
- Counts against: Promotional0.04
- Counts against: Overclaim0.20
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.58 | 0.45 | 0.72 | 0.58 | 0.27 | +0.24 | +0.140 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.70 | 0.70 | 0.90 | 0.77 | 0.20 | +0.26 | +0.199 |
| Audience breadthHow many people who build technology does it concern? | 0.58 | 0.50 | 0.62 | 0.57 | 0.12 | +0.13 | +0.074 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.66 | 0.80 | 0.88 | 0.78 | 0.22 | +0.22 | +0.171 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.44 | 0.60 | 0.78 | 0.61 | 0.34 | +0.05 | +0.030 |
| Technical depthHow technically substantive is it? | 0.87 | 0.70 | 0.72 | 0.76 | 0.17 | +0.05 | +0.038 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.91 | 0.85 | 0.92 | 0.89 | 0.07 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.05 | 0.05 | 0.03 | 0.04 | 0.02 | −0.19 | −0.008 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.28 | 0.20 | 0.12 | 0.20 | 0.16 | −0.11 | −0.022 |
| Sum of contributions | +0.668 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.668 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-30/36/"><img src="https://rubric.hrih.si/badge/2026-10-30/36.svg" alt="Ranked #36 on Rubric, 30 Oct 2026" width="245" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 30 Oct 2026, 05:47 UTC. It played no part in the ranking.