SWE Catalog
Home Browse Analysis About
Home / Catalog / Primary Impact / Security

Security

All SWE patterns tagged with Primary Impact: Security

6 SWE Patterns
Primary Impact
SWE-3003 2^ℵ₀

Insufficient Permission Granularity in Schema

Schema designs that lack proper permission granularity, allowing broad access to data through single permission grants. This includes friend-of-friend...

3 examples
SWE-3004 ℵ₁

Security Audit Trail Schema Weakness

Schemas that lack proper audit trail tables or security event logging structures, making it impossible to detect breaches, investigate incidents, or m...

3 examples
SWE-3005 ℵ₀

Insufficient Security Isolation in Schema

Schema designs that fail to isolate high-value or sensitive data from less critical data, creating single points of failure where compromise of one co...

3 examples
SWE-5001 2^ℵ₀

API Rate Limiting and Enumeration Weakness

APIs that lack proper rate limiting, use predictable identifiers (sequential IDs), and don't verify authorization for each request. This allows attack...

3 examples
SWE-5002 ℵ₁

Cloud IAM Permission Overreach

Cloud IAM roles and policies configured with excessive permissions, violating the principle of least privilege. This includes EC2 instances with broad...

3 examples
SWE-5004 ℵ₁

Third-Party Integration Security Weakness

Security vulnerabilities introduced through third-party integrations, including excessive permissions granted to vendors, lack of activity monitoring,...

4 examples

No SWE patterns found matching your criteria.

© 2025 Fetch Schema. Schema Weakness Enumeration (SWE) Catalog.

Preventing data integrity failures, one pattern at a time.