Report sample

Sample report

Sample

This is a fictional site (not a real company or service) that we ran through the actual checking system, with an example of our reviewer's comments added. The real report is delivered as a PDF of one to two pages.

Our reports are issued in Japanese, and this English version of the sample is for reference. If you need an English report, please tell us when you contact us and we will arrange it individually.

1. Overview

Target URL: http://bad.fixture.test/ (a fictional test site)
Date and time: (the actual report states the date and time)
Reviewer: (the actual report states the reviewer's name)

2. Summary

The most serious issue is that the front-end code contains a string that looks like a secret (an AWS access key ID). This needs to be checked first, before launch. Next, HTTPS support and the error display need attention. Item 2 can't be judged from outside, so it needs to be checked from the inside.

Counts: Fix before launch 6 / Can't be determined 1 / No issue 0 (we do not show percentages)

3. The seven items

ItemCategoryWhat we foundReviewer's comment (example)
1. Transport and certificatesFix before launchHTTPS is not supported (the site is served over HTTP only).Traffic could be read or tampered with by third parties.
2. Access protectionCan't be determined from outsideThe screen could be reached without authentication. Whether it is meant to be public or contains business data needs a human to judge.Whether this screen is meant to be public or holds business data can't be determined from outside.
3. Accidental exposureFix before launchThe error page for a non-existent path shows internal information (paths, exceptions, connection targets).The error page lets someone infer the internal structure.
4. Browser-side security settingsFix before launchNone of the main security-related response headers are set.No browser-side protections are in place.
5. External dependenciesFix before launchThe front-end code contains a string that looks like a secret (an AWS access key ID).Needs to be checked first, as the top priority.
6. Stability and responseFix before launchA raw exception is displayed for a non-existent path.The error display is unfriendly to users and also leaks internal information.
7. Signs of operationFix before launchNo link to a contact point, terms of use or privacy policy was found.If this is for business use, a contact point and terms need to be in place.

4. What we couldn't determine from outside

  • Protection and data handling behind the login (authenticated screens)
  • Code structure, tests and dependencies
  • Integration with existing systems, backup and recovery, operating structure

5. Your options

  • If you handle it yourself: check and fix the "Fix before launch" items before you go live.
  • If you proceed to the Production Readiness Assessment: we review the code and environment for what couldn't be determined from outside, and sort out the order and approach for fixing it.

6. Assumptions and disclaimer

  • This is an assessment of what can be observed from outside and does not guarantee safety.
  • It reflects the state of the site at the time of the check.
  • We did not run vulnerability scans, load tests or penetration tests, and did not probe non-public URLs.

In this sample, the categories and "What we found" were produced automatically by the checking system. The "Reviewer's comment" and the summary are written by a member of our team who reads your inquiry.

Talk to us about your own site