Authorization
Enforce authorization checks for external data source access in AI systems. Use when designing, configuring, or reviewing access controls between AI components and external databases or data services.
Install
$ agentstack add skill-redhatproductsecurity-prodsec-skills-authorization ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-redhatproductsecurity-prodsec-skills-authorization) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Authorization for External Data Sources
Security Requirement
It MUST be verified that the principal accessing an external data source has permissions to access or modify the data. Authentication alone (knowing who the principal is) is not sufficient; authorization (what they can do) must also be enforced.
Authorization Scope
| Operation | Authorization Check | |---|---| | Read data | Does the principal have read permission for this specific data? | | Write data | Does the principal have write permission? | | Modify schema | Does the principal have administrative permissions? | | Delete data | Does the principal have delete permission? | | Bulk export | Does the principal have permission for bulk data access? |
Principle of Least Privilege
Each AI system component should have only the minimum data access permissions needed:
| Component | Typical Permissions | |---|---| | RAG ingestion pipeline | Read-only on source data | | Inference engine | No direct data source access (goes through RAG) | | Agent with data tools | Read-only unless write is explicitly required | | Admin/maintenance jobs | Broader access, time-limited and audited |
Implementation Checklist
- [ ] Define the minimum data access permissions needed by each AI component
- [ ] Configure data source access controls to enforce least privilege
- [ ] Separate read and write permissions (do not grant write when only read is needed)
- [ ] Verify authorization on every data access request (not just at connection time)
- [ ] Regularly audit data source permissions and remove unnecessary access
- [ ] Use role-based or attribute-based access control at the data source level
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: RedHatProductSecurity
- Source: RedHatProductSecurity/prodsec-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.