BR-SEC-001: Security User Role & Token Scope REST Filter Restrictions

Mon, 01 Jan 0001 00:00:00 +0000

BR-SEC-001: Security User Role & Token Scope REST Filter Restrictions

Standard Classification: Role Definition & Behavioral Constraint / Access Control
Target Entity: User (Role: SECURITY_USER), Token (Scopes: READ, WRITE), Project, Vulnerability, REST Endpoints
Status: Approved
Enforcement Points: Backend Permissions (PermissionUtils, ProjectPermissions) and Resource Server (EndpointsFilter)

1. Executive Summary & Formal Statements

1.1 Formal Statement (RuleSpeak® / EARS)

While an authenticated user has the role SECURITY_USER:
- The system shall grant read access to all projects (including PRIVATE projects of any department or owner), but only to their Summary and Vulnerabilities information.
- The system shall deny access to clearing, ECC (Export Control and Customs), compliance, attachments, and license obligations details for those projects.
- The system shall not allow the user to create, modify, or delete core catalog entities across the system (strictly read-only role).
While an incoming REST API request is authenticated via an API Token or initiated by a SECURITY_USER:
- If the token possesses READ scope (or the authenticated user is SECURITY_USER):
  - The REST API Gateway (EndpointsFilter) shall intercept and block all HTTP POST, PUT, PATCH, and DELETE requests with HTTP 503 Service Unavailable / 403 Forbidden.
  - Otherwise, the gateway shall allow safe non-mutating query endpoints and self-service token lifecycle operations:
    1. POST /api/releases/batch-summary (Batch data retrieval requiring a JSON request payload).
    2. POST /api/users/tokens (Self-service generation of READ or WRITE scoped user API tokens from the UI/client).
    3. DELETE /api/users/tokens (Self-service revocation and cleanup of the user’s own API tokens).
- If the token possesses WRITE scope and the user is not SECURITY_USER, the system shall permit standard HTTP mutation verbs (POST, PUT, PATCH, DELETE) subject to standard domain permission checks.

1.2 Purpose & Risk Mitigated

The SECURITY_USER role and READ token scopes allow automated security scanners, audit tools, and read-only integrations global visibility into vulnerabilities and security posture across the entire organization’s software catalog without exposure to proprietary project internals, compliance data, or the ability to alter database records. Enforcing strict read-only behavior at the HTTP filter level guarantees defense-in-depth against unauthorized mutation attempts while explicitly allowing batch query POST requests and self-service token generation and revocation (to ensure users can manage their own security credentials and immediately invalidate compromised tokens).

Security Domain Business Rules on Eclipse SW360

BR-SEC-001: Security User Role & Token Scope REST Filter Restrictions

BR-SEC-001: Security User Role & Token Scope REST Filter Restrictions

1. Executive Summary & Formal Statements

1.1 Formal Statement (RuleSpeak® / EARS)

1.2 Purpose & Risk Mitigated