Research: Access control models for case-level OSINT data #52
Labels
No labels
agentic-osint
audit
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:preflight
blocked:verify-failed
bug
chore
deferred
enhancement
feature-request
in-progress
lint-baseline
lint-cleanup
needs-decompose
needs-triage
performance
quickfix
security/medium
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/osint-hub#52
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Research and evaluate access control approaches suitable for osint-hub. When complete, report findings back on issue osint-hub#36.
Scope
Deliverable
A written recommendation on which access control model to use, how it integrates with the existing user/auth system, and estimated complexity.
Post-Completion
Comment on osint-hub#36 with findings and a link to this issue.
Blocks
osint-hub#36 - No case-level access control
Fixed in commit. Closing.