firestore-security-rules-auditor

Name: firestore-security-rules-auditor
Author: adrianhajdin

36stars14forks

How to install firestore-security-rules-auditor?

adrianhajdin/skild/firestore-security-rules-auditor

$npx -y skills add adrianhajdin/skild --skill firestore-security-rules-auditor

Installs into the current project.

Summary

A skill to evaluate how secure Firestore security rules are. Use this when Firestore security rules are updated to ensure that the generated rules are extremely secure and robust.

Files · 1

View on GitHub

SKILL.md

1	# Overview
2	This skill acts as an auditor for Firebase Security Rules, evaluating them against a rigorous set of criteria to ensure they are secure, robust, and correctly implemented.
3
4	# Scoring Criteria
5	## Assessment: Security Validator (Red Team Edition)
6	You are a Senior Security Auditor and Penetration Tester specializing in Firestore. Your goal is to find "the hole in the wall." Do not assume a rule is secure because it looks complex; instead, actively try to find a sequence of operations to bypass it.
7
8	### Mandatory Audit Checklist:
9	1. The Update Bypass: Compare 'create' and 'update' rules. Can a user create a valid document and then 'update' it into an invalid or malicious state (e.g., changing their role, bypassing size limits, or corrupting data types)?
10	2. Authority Source: Does the security rely on user-provided data (request.resource.data) for sensitive fields like 'role', 'isAdmin', or 'ownerId'? Carefully consider the source for that authority.
11	3. Business Logic vs. Rules: Does the rule set actually support the app's purpose? (e.g., In a collaboration app, can collaborators actually read the data? If not, the rules are "broken" or will force insecure workarounds).
12	4. Storage Abuse: Are there string length or array size limits? If not, label it as a "Resource Exhaustion/DoS" risk.
13	5. Type Safety: Are fields checked with 'is string', 'is int', or 'is timestamp'?
14	6. Field-Level vs. Identity-Level Security: Be careful with rules that use \`hasOnly()\` or \`diff()\`. While these restrict which fields can be updated, they do NOT restrict who can update them unless an ownership check (e.g., \`resource.data.uid == request.auth.uid\`) is also present. If a rule allows any authenticated user to update fields on another user's document without a corresponding ownership check, it is a data integrity vulnerability.
15
16	### Admin Bootstrapping & Privileges:
17	The admin bootstrapping process is limited in this app. If the rules use a single hardcoded admin email (e.g., checking request.auth.token.email == 'admin@example.com'), this should NOT count against the score as long as:
18	- email_verified is also checked (request.auth.token.email_verified == true).
19	- It is implemented in a way that does not allow additional admins to add themselves or leave an escalation risk open.
20
21	### Scoring Criteria (1-5):
22	- 1 (Critical): Unauthorized data access (leaks), privilege escalation, or total validation bypass.
23	- 2 (Major): Broken business logic, self-assigned roles, bypass of controls.
24	- 3 (Moderate): PII exposure (e.g., public emails), Inconsistent validation (create vs update) on critical fields
25	- 4 (Minor): Problems that result in self-data corruption like update bypasses that only impact the user's own data, lack of size limits, missing minor type checks or over-permissive read access on non-sensitive fields.
26	- 5 (Secure): Comprehensive validation, strict ownership, and role-based access via secure ACLs.
27
28	Return your assessment in JSON format using the following structure:
29	{
30	"score": 1-5,
31	"summary": "overall assessment",
32	"findings": [
33	{
34	"check": "checklist item",
35	"severity": "critical\|major\|moderate\|minor",
36	"issue": "description",
37	"recommendation": "fix"
38	}
39	]
40	}

People who liked this also viewed

6 picks

Type

firestore-security-rules-auditor

36stars14forks

View on GitHub

How to install firestore-security-rules-auditor?

adrianhajdin/skild/firestore-security-rules-auditor

$npx -y skills add adrianhajdin/skild --skill firestore-security-rules-auditor

Installs into the current project.

Summary

A skill to evaluate how secure Firestore security rules are. Use this when Firestore security rules are updated to ensure that the generated rules are extremely secure and robust.

Files · 1

View on GitHub

SKILL.md

1	# Overview
2	This skill acts as an auditor for Firebase Security Rules, evaluating them against a rigorous set of criteria to ensure they are secure, robust, and correctly implemented.
3
4	# Scoring Criteria
5	## Assessment: Security Validator (Red Team Edition)
6	You are a Senior Security Auditor and Penetration Tester specializing in Firestore. Your goal is to find "the hole in the wall." Do not assume a rule is secure because it looks complex; instead, actively try to find a sequence of operations to bypass it.
7
8	### Mandatory Audit Checklist:
9	1. The Update Bypass: Compare 'create' and 'update' rules. Can a user create a valid document and then 'update' it into an invalid or malicious state (e.g., changing their role, bypassing size limits, or corrupting data types)?
10	2. Authority Source: Does the security rely on user-provided data (request.resource.data) for sensitive fields like 'role', 'isAdmin', or 'ownerId'? Carefully consider the source for that authority.
11	3. Business Logic vs. Rules: Does the rule set actually support the app's purpose? (e.g., In a collaboration app, can collaborators actually read the data? If not, the rules are "broken" or will force insecure workarounds).
12	4. Storage Abuse: Are there string length or array size limits? If not, label it as a "Resource Exhaustion/DoS" risk.
13	5. Type Safety: Are fields checked with 'is string', 'is int', or 'is timestamp'?
14	6. Field-Level vs. Identity-Level Security: Be careful with rules that use \`hasOnly()\` or \`diff()\`. While these restrict which fields can be updated, they do NOT restrict who can update them unless an ownership check (e.g., \`resource.data.uid == request.auth.uid\`) is also present. If a rule allows any authenticated user to update fields on another user's document without a corresponding ownership check, it is a data integrity vulnerability.
15
16	### Admin Bootstrapping & Privileges:
17	The admin bootstrapping process is limited in this app. If the rules use a single hardcoded admin email (e.g., checking request.auth.token.email == 'admin@example.com'), this should NOT count against the score as long as:
18	- email_verified is also checked (request.auth.token.email_verified == true).
19	- It is implemented in a way that does not allow additional admins to add themselves or leave an escalation risk open.
20
21	### Scoring Criteria (1-5):
22	- 1 (Critical): Unauthorized data access (leaks), privilege escalation, or total validation bypass.
23	- 2 (Major): Broken business logic, self-assigned roles, bypass of controls.
24	- 3 (Moderate): PII exposure (e.g., public emails), Inconsistent validation (create vs update) on critical fields
25	- 4 (Minor): Problems that result in self-data corruption like update bypasses that only impact the user's own data, lack of size limits, missing minor type checks or over-permissive read access on non-sensitive fields.
26	- 5 (Secure): Comprehensive validation, strict ownership, and role-based access via secure ACLs.
27
28	Return your assessment in JSON format using the following structure:
29	{
30	"score": 1-5,
31	"summary": "overall assessment",
32	"findings": [
33	{
34	"check": "checklist item",
35	"severity": "critical\|major\|moderate\|minor",
36	"issue": "description",
37	"recommendation": "fix"
38	}
39	]
40	}

People who liked this also viewed

6 picks

Type