Repository navigation
Which attack stage should Rejewski emulate next? #148
Pinned
dermo-blast
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Rejewski v1.0 covers Stage 1: a stolen standard account signs in, reuses its token, and reads the tenant through 15 read-only Microsoft Graph tools. Each release adds the next stage of the attack, and I'd like the next ones shaped by the people who assess real tenants.
Stage 2 is proposed as Persistence (ADR 0009, status Proposed): what the same stolen standard account can plant to keep access. The candidates:
Every write would be named in the run's consent record, rolled back in the same run, and confirmed gone with a read.
Three questions:
A specific case helps more than a vote: the tenant setting that made it possible and how you found it. Please leave out tenant names, IDs, and anything that identifies a real organization.
If you have run Rejewski against your own lab, a reply saying so helps too.
All reactions