Django access control review

Audits Django and DRF code for IDOR and broken access control by learning the app's authorization model and tracing each endpoint from ID to query, reporting only confirmed gaps with enforcing fixes. Use when reviewing views, viewsets or tenant isolation.

SecurityPack: Sentry skillslinkdjango-access-review
Author
Source
getsentry/skills/skills/django-access-review @ a582c51
License
Apache-2.0

About this skill

What it does

The skill audits Django and DRF code for broken access control and IDOR around one question: can user A read, change or delete user B's data? Pattern matching is ruled out. The agent first learns how this codebase enforces authorization (decorators, middleware, base views, DRF permission classes, custom managers, get_queryset()) and what the ownership model is: user, organisation, tenant or a hierarchy. SKILL.md gives grep commands for this and forbids moving on before then.

The agent then traces each endpoint with user data from where the ID enters (URL, query string, body) to the query that fetches the object, looking for the check in between. Follow-up questions cover list filtering, who sets the owner on create, bulk operations, related objects and swapping org_id in the URL. A worked example traces a ModelViewSet with IsAuthenticated and Document.objects.all() to a confirmed IDOR.

Only confirmed findings are reported: high confidence means the flow was traced and no check exists, medium goes under "needs manual verification", low is dropped. A suggested fix must enforce the rule in code; a comment asking the caller to check permissions does not count. Each finding comes with location, evidence and a fix.

references/ holds four background notes: django-orm.md (scoping managers), django-views.md (layers from URL conf to query), drf-permissions.md (why a direct Model.objects.get skips has_object_permission) and tenant-isolation.md (where the tenant comes from). SKILL.md does not point to them; ask the agent to read them.

When to use it, and when not

Use it on views, viewsets and ORM code that decide who sees what, especially in multi-tenant apps.

It covers authorization in Django only.

How to run it

We do not copy this skill: its own SKILL.md says its reference material is based on the OWASP Cheat Sheet Series under CC BY-SA 4.0, while the repository is Apache-2.0. Install it from the author's repository; the button on this page leads there. The author's README offers a Claude Code plugin with the whole Sentry set (claude plugin marketplace add getsentry/skills, then claude plugin install sentry-skills@sentry-skills) or npx skills add getsentry/skills for other agents. The agent picks the skill up by its description when you mention IDOR or access control; to call it yourself:

  • Claude Code with the plugin: /sentry-skills:django-access-review, or ask for the skill by name.
  • Codex: $django-access-review.
  • Cursor: type / in the Agent chat and pick django-access-review.

Example: /sentry-skills:django-access-review Can a member of one organisation reach another organisation's invoices through our API?

How it differs from similar skills

Security review, Sentry covers every vulnerability class with the same confidence levels; this skill goes deeper on one class in one framework. Security review from our catalog traces untrusted input to sinks for any stack. Find bugs in branch changes has IDOR as one item of eleven. Django performance review is the companion for N+1 queries and unbounded querysets.

Install

This skill is not copied to the catalog. Install it from the author's repository.

Open the source

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack Sentry skills

AGENTS.md and CLAUDE.md writer

Writes or trims a repository's AGENTS.md to under 60 lines of commands, conventions and pointers to existing docs, checks every path, and makes CLAUDE.md a symlink to it. Use when a repo needs agent instructions or its current file has grown long or stale.

Claude Code settings audit

Detects a repository's stack and proposes a Claude Code settings.json allow list of read-only commands for the tools it actually uses, plus docs domains and Sentry or Linear MCP entries. Use when setting up Claude Code permissions or auditing existing ones.

Code review, Sentry practices

Reviews a change by Sentry's guidelines: runtime errors, performance and N+1 queries, side effects, compatibility, security, design and tests, with a polite tone and approval once only minor issues remain. Use when reviewing a pull request or branch.

Code simplifier

Simplifies recently changed code without changing behaviour: less nesting, no nested ternaries, clearer names, no redundant abstractions, while following CLAUDE.md conventions. Use when code works but reads heavier than it should and needs a cleanup pass.

Conventional commit messages

Commits in Sentry's Conventional Commits style: a feature branch instead of main, a typed capitalised subject up to 70 characters, Fixes or Refs footers, no personal data. Use when asked to commit changes or draft a commit message.

Find bugs in branch changes

Reviews the commits on the current branch for security holes, bugs and quality issues with an eleven-item checklist and reports verified findings with file, line, severity and fix, without editing code. Use when you want a security-first pass before a PR.

GitHub Actions security review

Audits GitHub Actions workflows for attacks an outsider without write access can run: pwn requests, expression injection, comment commands, token theft, poisoned agent configs, unpinned actions. Use when reviewing CI security or changing workflows.

Iterate a PR until CI is green

Drives an open PR to green: fixes failing CI and high and medium review comments, verifies locally, commits, pushes and repeats, stopping at human approval or draft gates. Use when a PR is red or has review feedback to work through.

PR title and description writer

Writes or refreshes a PR title in Sentry's conventional format and a short reviewer-facing description without template headings or test logs, then opens a draft or updates the PR. Use when opening a PR or after commits change its scope.

Prompt optimizer

Writes, repairs or ports system and agent prompts against a small eval set, comparing candidate rewrites on the same cases and checking the winner on held-out ones. Use when a prompt is unreliable, moves to another model family or needs evals.

Secret leaks through serialization

Finds secrets that leak when a credential field on a dataclass, pydantic model or JS object meets code that logs or traces whole objects, searching the whole repository for the other half. Use when a change adds such a field or a wholesale sink.

SECURITY_MODEL.md for review tools

Writes and maintains SECURITY_MODEL.md, telling security review tools a repository's exposure, invariants, reportable finding classes and owner-confirmed exclusions, with a script that flags stale references. Use when preparing a repo for automated review.

Agent skill security scanner

Audits an agent skill before installation: a static scan for prompt injection, hidden Unicode, secrets, risky scripts and structural traps, then a review of intent and permissions ending in a verdict. Use when a skill comes from an outside source.

Skill writer by the Agent Skills spec

Creates and improves agent skills by Sentry's workflow: sources with provenance, the simplest execution shape, SPEC.md and SOURCES.md, precision passes after each change and a structural validator. Use when building a skill that a team will maintain.

Security review, Sentry

Reviews a file, diff or component for exploitable vulnerabilities with OWASP-based references, researches the codebase before flagging and reports only findings reached by attacker-controlled input. Use when a change needs a low-noise security review.

Django performance review

Reviews Django and DRF code for N+1 queries, unbounded querysets, missing indexes and write loops, validating table size and hot paths before reporting. Use when a Django view or endpoint is slow or a change touches large tables.