auditing-jit-provisioning-and-role-mapping SKILL.md skillA
auditing-jit-provisioning-and-role-mapping from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/auditing-jit-provisioning-and-role-mapping@git:20260903.19a7174Pins git:20260903.19a7174 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/auditing-jit-provisioning-and-role-mapping/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260903.19a7174, committed Sep 3, 2026
- Size
- 11,207 bytes
- Repository stars
- 26
- License
- MIT
Audit just-in-time account provisioning at federated (SAML or OIDC) login for trust misplaced in the assertion that drives it: a first login that creates an account and assigns roles from identity-provider claims (groups, email domain, department) the service never validates, a claim-to-role mapping that grants more privilege than the claim should or defaults new users into a privileged role, an email or domain claim trusted to auto-join a tenant so an attacker with a lookalike address lands…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Auditing JIT provisioning and role mapping: the first login decides the role, from claims you did not issue Just-in-time provisioning creates a local account the first time someone logs in through a federated identity provider, and often updates that account's roles on every subsequent login, all from the claims in the login assertion. The claims, group memberships, an email, a domain, a department, come from the identity provider, not from you, so JIT hands account creation and role assignment to whatever the assertion says. That is fine when the mapping is tight and the claims are validated, and dangerous when either is loose. A claim-to-role mapping that grants more privilege than the claim should, or defaults every new user into a privileged role, elevates at first login. An email or domain claim trusted to auto-join a tenant or organization lets an attacker with a lookalike or attacker-controlled address land inside it. A JIT update that re-reads mutable claims every login can re-elevate or reassign an account an admin previously corrected. And any claim provisioned without validation, an unverified email, a group the attacker can influence, an unsigned or overtrusted …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/auditing-jit-provisioning-and-role-mapping@sha256:f5122f2feaf21755The line at the top of this page pins the label git:20260903.19a7174, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pur6jduz5muwkgvn)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11207 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pur6jduz5muwkgvn GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/auditing-jit-provisioning-and-role-mapping GET https://markdownregistry.com/api/v1/blob/f5122f2feaf21755a79a803aaf47f96c7e8f6ebeea832b761aac9d71373916fe
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.