Works with the AI Agents you already use
Srednoff Firebase Auth & Security Rules Auditor
Produce a rule-path decision table, Auth/custom-claim boundary review and emulator retest specification with rule-level remediation proposals, not automatic deployment or a runtime scanner.
$7.99
Srednoff Firebase Auth & Security Rules Auditor
Example session with this skill installed
Audit these Firestore and Storage rule snapshots for tenant isolation and owner-field updates.
- Read your context and instructions
- Compiled the srednoff firebase auth
Expected report shape, not a completed real audit: Executive Summary; Scope; Evidence Reviewed
Connects securely to your tools. The creator never sees your data.
About this skill
Srednoff Firebase Auth & Security Rules Auditor
One-Line Outcome
Produce a rule-path decision table, Auth/custom-claim boundary review and emulator retest specification with rule-level remediation proposals, not automatic deployment or a runtime scanner.
Short Description
An authenticated UI and passing Admin SDK tests can conceal public wildcard grants, mutable ownership and rules that never protect privileged server operations.
Problem It Solves
An authenticated UI and passing Admin SDK tests can conceal public wildcard grants, mutable ownership and rules that never protect privileged server operations.
Firebase backend owner: rule/path/custom-claim access matrix, Admin SDK trust boundary and emulator test specification with rule-level remedies.
What You Get
- Executive Summary
- Scope
- Evidence Reviewed
- Service And Rules Target Map
- Principal Path Operation Matrix
- Auth Claims And Admin Boundary
- Rule-Level Remediation Proposals
- Emulator Test Ledger
- Findings
- Prioritized Action Plan
- Quick Wins
- High-Risk Items
- Missing Evidence
- Unknowns
- Next Validation Steps
- Rollback And Offline Compatibility Risks
How It Works
- Establish read-only scope, revision and exact Firebase services. Map every app/database/bucket alias to a supplied rule file without accessing accounts. Confirm Firestore mode/edition; do not transplant these Rules assumptions to MongoDB compatibility or Realtime Database.
- Build a principal matrix: unauthenticated, owner, same-tenant non-owner, foreign tenant, privileged role and removed member. Distinguish anonymous Firebase Auth accounts from request.auth == null and document intended public data.
- Trace backend Auth verification: Firebase ID token versus custom sign-in token, project-bound audience/issuer, signature, expiry and verified UID. Review custom-claim issuer authority and explicit revocation-check policy; ordinary token verification is not assumed to check revocation. Separate client display fields, signed claims and server-owned membership records without reading or issuing real tokens.
- Expand relevant Firestore match paths and operations, including get versus list, create/update/delete, subcollections and collection-group queries. Evaluate all overlapping allows together; a narrow deny does not override a broader matching grant.
- Review ownership and schema transitions using existing resource versus proposed request.resource data. Protect owner, tenant and role fields from reassignment; handle missing fields, deletes and allowed-field/type constraints per operation rather than applying one predicate blindly.
- Compare client query constraints with list rules. Rules are not result filters; document which query shapes are permitted and test intended lists without weakening isolation. Review batched/transactional invariants and rules-access budgets where they are used.
- Review Storage rules separately: bucket/path ownership, read/list/create/update/delete, metadata mutation, declared type and size conditions. Metadata/type checks do not inspect malware or validate actual byte content; hand that concern to the upload pipeline review.
- Trace Admin SDK and service-account paths outside client Rules enforcement. Require application-side authorization and least-privileged IAM evidence; a rules patch does not repair an unguarded privileged function.
- Inspect emulator isolation: demo project, explicit localhost routing, explicit rules loading/digest and clean fixture lifecycle. Seed setup may bypass rules only in isolated authorized tests; the assertions under review must execute as normal authenticated or unauthenticated client contexts.
- Design a local decision matrix for legitimate owner operations, cross-user/tenant denials, public reads, owner-change attempts, claim downgrade, unsupported query and Storage metadata updates. Record expected/actual separately and keep any unrun test NOT_EXECUTED.
- Propose rule-level changes by exact match path, operation, intended invariant and before/after behavior. Provide a minimal predicate sketch or patch proposal only when schema evidence supports it; never supply a blanket allow rule or deploy automatically.
- Return findings and a target-bound retest/rollback handoff. Highlight app compatibility, offline queued writes and privileged-server residual risk; restoration of an old rule revision requires owner approval and must not silently restore a known public grant.
Best For
Firebase application owners and reviewers responsible for client data access and privileged backend paths
Example Tasks
- Audit these Firestore and Storage rule snapshots for tenant isolation and owner-field updates.
- Review why Admin SDK tests pass while normal Firebase clients lack authorization coverage.
- Produce rule-path remediation and a local emulator matrix for custom claims and removed members.
Inputs
- Authorized revision, redacted Firebase project/database/bucket aliases, product/edition and SDK/tool versions
- firebase.json rules mappings plus exact Firestore and Storage rule snapshots; deployed revision evidence if available
- Synthetic collection/object schema, owner/tenant/role model, client queries and intended public paths
- Sanitized authentication, custom-claim issuance and Admin SDK/backend authorization handlers
- Emulator configuration, explicitly loaded rules digest and revision-linked client-context test results, if any
Outputs
- Executive Summary
- Scope
- Evidence Reviewed
- Service And Rules Target Map
- Principal Path Operation Matrix
- Auth Claims And Admin Boundary
- Rule-Level Remediation Proposals
- Emulator Test Ledger
- Findings
- Prioritized Action Plan
- Quick Wins
- High-Risk Items
- Missing Evidence
- Unknowns
- Next Validation Steps
- Rollback And Offline Compatibility Risks
Permissions
Read-only review of owner-supplied artifacts by default. Report file writes, shell/local fixture execution and official documentation lookup are optional, require available tools and their explicit scope. No live credentials are requested.
Compatibility
Standalone workflow, no Srednoff OS dependency. Codex evidence is synthetic entrypoint text only when recorded below. Claude Code, Cursor and actual buyer-runtime task delivery remain UNTESTED. Provider/platform-specific contracts must be refreshed for the installed version.
Limitations
This is an instruction/evidence workflow, not a hosted security service, persistent enforcement engine, production certification or business guarantee. The optional Python helper checks supplied claims, not underlying source artifacts. Agensi delivery is agent-only: do not save/export proprietary skill files to run local helpers; disclose NOT_EXECUTED where execution is unavailable.
Validation Transparency
Offline evidence-precheck status: PASS. Authored synthetic text-response cases: 19/19, status PASS. This is not independent security testing, complete artifact inspection or proof of deployment safety. Exact-text hashes and attempts are retained separately.
License And Publisher
Commercial License 1.0 covers original new expression; historical MIT and third-party rights remain unchanged. Mandatory marketplace conditions prevail. Publisher: Ivan Srednoff / Srednoff.Agency. No proprietary source resale or off-platform paid upsell is included.
FAQ
What is different from a generic security request? Firebase backend owner: rule/path/custom-claim access matrix, Admin SDK trust boundary and emulator test specification with rule-level remedies. No whole-SaaS tenant audit, upload parser review, generic cloud IAM audit, deployed rules changes or claim that emulator tests were run when not run.
Does it change production automatically? No. Audit/design is the default; changes, secret rotation, IAM, network probes and financial actions need separate explicit authorization.
Are the examples real incidents? No. They are synthetic DEMO DATA.
Is this a certification or guaranteed protection? No. Evidence gaps, residual risk and unexecuted tests remain explicit.
Can I use project-specific reports for clients? Yes under the included license; proprietary workflow source is not a client deliverable.
Version
1.0.0
Release Notes
Initial scoped security workflow with domain decision rules, evidence requirements, synthetic examples, regression cases and explicit authorization/runtime limits. No production/customer outcome is claimed.
This is an instruction/evidence workflow, not a hosted security service, persistent enforcement engine, production certification or business guarantee. The optional Python helper checks supplied claims, not underlying source artifacts. Agensi delivery is agent-only: do not save/export proprietary skill files to run local helpers; disclose NOT_EXECUTED where execution is unavailable.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 day ago