Blackbox Assessment
The English user guide is currently in beta preview. Most of the documents have been automatically translated from the Japanese version. Should you find any inaccuracies, please reach out to Flatt Security.
Overview
Takumi's blackbox assessment feature receives an application's URL and authentication information, performs simulated attacks on the application, and outputs assessment results as a report on the web. The diagram below shows how an assessment proceeds.

It can be used from the Shisho Cloud byGMO web interface.
Organization or Target Ownership Verification
Before starting an assessment, you need to verify your organization or prove ownership of the target application for blackbox assessment. For details, please refer to "Pre-Assessment Organization Verification or Ownership Verification".
How to Start an Assessment
Click "Assessments" in the sidebar, then click the "Create Assessment" button in the upper right corner of the screen to start an assessment.
Carry Over Settings from an Existing Assessment
When you want to run a new assessment with the same settings as a previous one, you can carry over the configuration of an existing assessment instead of filling in the form from scratch. Follow these steps:
- Click the "Create Assessment" button in the upper right corner of the assessment list.
- Select "Create from existing assessment" in the dialog.
- Choose the assessment whose settings you want to carry over.
The creation form opens pre-filled with the selected assessment's configuration. Review and adjust the settings, then start the assessment.
You can also use this feature to retry an assessment that failed during execution, keeping the same settings.
Assessment Configuration
The main items on the configuration screen are:
- Assessment Name: Enter a name to identify this assessment.
- Report Language: Select the language of the assessment report (English or Japanese).
- Assessment Method: Select "Blackbox Assessment".

Target Type
Under "Target Type", you can select the form of the target application from the following two options:
- Web application: An application operated through a web browser.
- API: An API without a screen.
When you select "API", Takumi extracts the endpoints to assess from the attached schema files instead of crawling with a web browser. For the differences in the settings, see Assessing an API.
Assessment Type
You can select one of the following two modes:
- Full Assessment: Crawling and the initial scan of the target application are performed in one seamless process. After completion, the assessment pauses in a "Pending" state.
- Scoped Assessment: Takumi stops at the end of crawling. After that, you set priorities for the features and perspectives you want to assess, as well as the credit threshold for the scan, then resume the assessment.
Credit Threshold
Credit thresholds can be set separately for crawling and scanning (for "Scoped Assessment" mode, only crawling). Takumi performs crawling and scanning within the specified credit thresholds.
Web Application Settings
The web application settings are:
- URLs to start crawling from: Enter the URLs of the application where crawling starts.
- Authentication Information: Configure the credentials for logging into the application.
- Client Certificate (mTLS): Upload the TLS client certificate the application requires (PKCS#12 or PEM), and choose the hosts to present it to.
- In-Scope URLs / Out-of-Scope URLs: Narrow down or exclude the crawl range (see Scope Settings for details).
Takumi does not create new accounts during the assessment; it uses only the pre-configured credentials to log in. The following authentication methods are supported:
- ID / password authentication
- TOTP (Time-based One-Time Password) authentication using a pre-shared secret code
- One-time codes delivered by email, using "Takumi-managed email" (see Signing In With an Emailed One-Time Code)
Out-of-band authentication methods that do not go through email, such as SMS code verification, are not currently supported.
Signing In With an Emailed One-Time Code
When the target application sends a one-time code by email at sign-in, Takumi cannot read a code delivered to your own mailbox. In that case, select a Takumi-managed email address from the assessment screen and use it instead.
This is not limited to multi-factor authentication codes — any message the application delivers by email, such as a magic link or a sign-up confirmation, can be read this way.
Configuration Steps
Add a credential under "In-App Authentication", then set "Account Email" to "Takumi-managed email". After that, click "Issue a new address" to obtain an address, or select one that has already been issued. The issued address is set as the credential's ID.

Be sure to create the account on the target application with that address before running a crawl or an assessment.
Once mail has arrived, the same screen shows when it was last received, which lets you confirm that the target application really delivers to the address. Until anything arrives, it shows that no mail has been received yet. When the delivery status cannot be retrieved, it says so rather than reporting that no mail has arrived.
Up to 5 addresses can be issued per organization. An issued address cannot be released, so reuse the addresses you already hold across assessments rather than issuing a new one each time.
Scope Settings
Takumi crawls starting from the URLs you provide and, by default, treats the whole domain of those URLs as in scope. When you want to assess only a part of the application, you can narrow or exclude the crawl range with the following two settings.
In-Scope URLs narrow down the range included in the crawl results. How the range is limited depends on the form of the URL you specify.
- A URL with a path (e.g.
https://app.example/admin): limits the range to that path and below - A URL without a path (e.g.
https://app.example): limits the range to that host only - Left empty: covers the whole domain of the URLs to start crawling from
Out-of-Scope URLs specify URLs to exclude from the crawl results. As with In-Scope URLs, the excluded range depends on the form of the URL you specify.
- A URL with a path (e.g.
https://app.example/admin/logout): excludes that path and below - A URL without a path (e.g.
https://app.example): excludes that entire host
Out-of-Scope URLs always take precedence over In-Scope URLs. Even when a URL is included by the URLs to start crawling from or by In-Scope URLs, any URL that matches an Out-of-Scope URL is excluded from the crawl results.
Scope settings are used to decide whether a URL discovered during crawling is included in the assessment targets (the crawl results). For this reason, even a URL that is out of scope or not included in the crawl results may still be accessed by Takumi during crawling or assessment. Note that scope settings do not completely block such access.
Assessing an API
When you select "API" as the "Target Type", you can assess an API without a screen. Takumi does not crawl with a web browser; instead, it extracts the endpoints to assess from the attached schema files. The assessment flow after endpoint extraction is the same as for a web application.
The settings differ from a web application in the following points:
- API root URL: Enter a single root URL of the API to assess
- API schema files: Attach one or more schema files that define the API specification (OpenAPI Spec, GraphQL schema, etc.)
- Authentication Information: When the API requires authentication, provide the detailed authentication steps (such as how to obtain a token and which headers to set) in the "Authentication Steps" field, along with the ID / password and other credentials
Additional crawls are not available for API assessments. To add endpoints to assess, use Manual Editing of Crawl Results.
Reviewing Crawl Results and Running Additional Crawls
Setting Priorities and Credit Threshold
If you select "Scoped Assessment" mode, the assessment pauses after crawling completes. Opening the assessment page displays a matrix of detected features and assessment perspectives.
On this screen, you can set the credit threshold for scanning and assessment priorities to start the assessment.

You can set priorities of "Auto, High, Medium, Low, None" for each combination of feature and perspective. Higher-priority items are scanned first. When "Auto" is selected, Takumi automatically determines the priority based on risk analysis.
Combinations that are never assessed are shown as "Skipped" and take no priority. See Assessment Perspectives for which combinations these are.
Once priorities and the credit threshold are configured, click the "Start Pentesting" button to begin the scan.
Additional Crawl
When an assessment is in the "Crawled" state, you can select "Additional Crawl" from the menu to run additional crawling. This is useful when you want to discover endpoints that were not found during the initial crawl.
The following settings are available for additional crawls:
- Credit Threshold: The maximum credit limit for the additional crawl
- Additional Crawl Instructions: Free-form instructions to guide the crawl toward specific areas (e.g., focusing on specific API paths)
When the additional crawl completes, newly discovered endpoints are added to the matrix.
Running an additional crawl does not guarantee that new endpoints will be discovered. Credits are consumed even if no new endpoints are found.
Manual Editing of Crawl Results
When an assessment is in the "Crawled" state, you can manually edit the crawl results by clicking the "Edit Crawl Results" button displayed at the bottom-left of the priority matrix on the assessment page.
On this page, the following operations are available:
- Add endpoints to a detected feature
- Remove endpoints from a detected feature
- Add new features along with their endpoints

Reviewing Results and Running Additional Scans
When the credit threshold is reached during a scan or all selected combinations have been scanned, the assessment pauses in a "Pending" state.
Opening a "Pending" assessment displays the matrix screen again. Each cell shows one of the following states:
| State | Description |
|---|---|
| Scanned | Displayed for combinations where scanning has completed |
| Skipped | Displayed for combinations that were skipped because scanning was deemed unnecessary |
| Priority menu | Displayed for combinations that have not yet been scanned |

From this screen, you can:
- Preview the interim report: Click "Preview Report" to open the current report in a new tab
- Run additional scans: Set the credit threshold and priorities for unscanned combinations, then click "Start Pentesting" to run additional scans
- Complete the assessment: If no additional scans are needed, click the "Complete Assessment" button to finalize the assessment