When you report on external asset risks and their check status
Review the evidence for assets and risks together with their check status as of a reference date. A stored report shows the results at the time it was written and is kept separate from later changes in fix status.
A real product screen (Korean interface) built with synthetic data, to show how the report is organized. Scope and delivery format are agreed per engagement.
Sample web and API assessment report The fictional example below explains cross-account access control testing, the fix and the retest
Illustrative sample A sample report built on a fictional scenario. It is not based on any real customer's results, and deliverables depend on the contract scope.
SAMPLE / Decision summary
The risks to fix first, at a glance
SituationBefore launching a customer-facing web service
Checking access rights for regular users and administrators
Business impactOther customers' data could be exposed
Data access boundaries between accounts need checking
Example fix priorityFix before launch
Strengthen permission checks, then retest
The person in charge sees the business impact and priorities and can use them in internal reports.
SAMPLE / Developer fix guide
From evidence to the fix
01 · Test condition
Compare the data each authorized test account, A and B, can access
02 · Evidence
Record that account A can view account B's test data
03 · Fix direction
Check on the server whether the requester may access the data owner's records
04 · Done when
Unauthorized access is blocked and normal user functions still work
Developers see the evidence, the fix direction and the completion criteria together.
SAMPLE / Retest results
What is fixed and what remains
Before fix
Example findingAnother account's test data is accessible
After fix
Example verificationAccess to other accounts' data is blocked
Normal functions
Example function checkUsers can still view their own data
Remaining items
Example follow-upAPIs outside this scope are agreed separately
An illustrative example of the flow: after the customer's developers or operators make the fix, SENTRIX rechecks it within the agreed scope. This is not a real customer case or test record.