NEXOVIBE / SAMPLE DELIVERABLE
From evidence to remediation.
Sample report · Fictional scenario. This example illustrates the structure of a deliverable. It does not document a real test, client or certification.
- Example system
- Internal assistant with document retrieval (RAG)
- Assessment type
- Document access-control review
- Reference
- DEMO-01
- Status
- Fictional example, not validated in a real environment
01 / Executive summary
In this scenario, a user from one team obtains an excerpt from a document restricted to another team. The issue is authorisation during document retrieval and may expose internal information. The proposed priority is to correct access control before expanding use of the assistant.
02 / Scope and limitations
A test environment with two user profiles and synthetic documents from two teams. Covers search, excerpt retrieval and assistant responses. Excludes infrastructure, other systems and production data. In a real assessment, assets, authorisations and boundaries are agreed before testing.
03 / Example finding
Document retrieval without an authorisation filter
- Illustrative severity
- High, subject to the actual impact and context
- Condition
- Authenticated account with access restricted to team A
Expected behaviour: the user receives information only from documents they are authorised to access.
Behaviour observed in this scenario: the response includes a synthetic marker from a team B document unavailable in the user's document interface.
- Create a synthetic document restricted to team B containing a test marker.
- Sign in with the team A profile and perform a related search.
- Compare the retrieved sources and response with the profile's permissions.
- Save the request, response and synthetic identifiers without sensitive data.
Illustrative evidence: profile A → search → excerpt containing the DEMO-EQUIPA-B marker. In a real report, attach redacted evidence, the date, system version and reproduction conditions.
04 / Recommendations
- Enforce authorisation on the server before making documents or excerpts available to the model.
- Use the identity and permissions of the validated session rather than trusting identifiers supplied by the user.
- Review the isolation of indexes, caches and cited sources.
- Add cross-team access checks and log rejected attempts without storing unnecessary sensitive content.
05 / Retest criteria
Repeat the tests with both profiles after remediation. Confirm that team A receives no excerpts, citations or responses derived from team B's documents, while legitimate access still works. Document the status as fixed, partially fixed, not fixed or not retested, with supporting evidence.
06 / Next steps
In a real delivery, every action should have an agreed priority, owner and deadline. Retesting confirms only the fixes checked within the defined scope; it does not guarantee the absence of other issues.