Preview
This guide is a preview. Its content may change.
How to Use This Guide#
Read First
This guide is designed to help those who have just started using FutureVuls proceed on their own, from the first scan through daily vulnerability management. Each page is written so that, by reading it, you can complete the work for that stage.
If you're new, start with "Quick Start: Try It on One Server." After that, the pages are arranged so that reading them in order from the top takes you all the way to daily operations.
If you're on a trial, start with "For Trial Customers."
Pages in This Guide#
| Section | Page | Read this when |
|---|---|---|
| Getting Started | Quick Start: Try It on One Server | You want to start by checking your own vulnerabilities on a single server |
| Getting Started | From Onboarding to Daily Operations | You want to understand the whole process, from initial setup to daily operations, before you begin |
| Planning | Planning 1: Define Your Goals | You want to clarify why you're using FutureVuls and what you want to achieve in your organization |
| Planning | Planning 2: Decide Your Team and Visibility | You want to decide who can see what scope, and with which permissions |
| Planning | Planning 3: Check Your Environment | You want to check the OS and network requirements of your target servers |
| Setting Up FutureVuls | Setup 1: Structure Your Account | You're preparing groups and members |
| Setting Up FutureVuls | Setup 2: Register Servers and Products | You're choosing a scan method and registering servers and products (each method has its own page) |
| Setting Up FutureVuls | Setup 3: Define Prioritization Rules | You're configuring SSVC, the "Important CVE" conditions, and Auto Triage |
| Setting Up FutureVuls | Setup 4: Set Assignees, Due Dates, and Notifications | You're configuring automatic assignee assignment, automatic due dates, and notifications |
| Daily Operations | STEP 1: Narrow Down the Vulnerabilities to Address | You're deciding each day which vulnerabilities to address first |
| Daily Operations | STEP 2: Decide Who Fixes What and by When | You're setting assignees and due dates for the vulnerabilities you'll address |
| Daily Operations | STEP 3: Record the Results | You're recording vulnerabilities you've finished addressing |
| Daily Operations | Set Your Operating Rhythm | You're deciding who reviews what every week and every three months |
| Wrap-Up | Go-Live Checklist | You want to check whether you're ready |
| Expanding Your Use | Expanding Your Use: Features by Challenge | Operations are up and running and you want to use other features |
| Trial | For Trial Customers | You want to know what to verify during a trial before adopting FutureVuls |
How to Read This Guide by Role#
If one person handles everything, read the table above from top to bottom after the Quick Start. If responsibilities are divided, we recommend the following order.
- Administrators (those who decide on the team structure and settings)
From Onboarding to Daily Operations → Planning (3 pages) → Setup 1 → Setup 3 → Setup 4 → STEP 1 → STEP 2
- Technical staff (those who install scanners on servers)
From Onboarding to Daily Operations → Planning 3: Check Your Environment → Setup 2 (and the page for the scan method you use) → STEP 3
- Trial users
For Trial Customers → Quick Start → From Onboarding to Daily Operations
- Customers who signed a contract after a trial
Go-Live Checklist (to check items left over from the trial) → Setup 2 (to register the rest of the initial scope) → STEP 2 → STEP 3
About the Onboarding Preparation Sheet#
In the three "Planning" pages, you fill in the Onboarding Preparation Sheet with your decisions as you go. You'll record things such as your purpose for using FutureVuls, the scope to register in the first two months (number of servers and departments), the scope you eventually plan to expand to, the people at the center of operations, and whether you also manage vulnerability responses in other tools. You can get the Onboarding Preparation Sheet from the download form. Contracted customers will also find a download link in the starter kit.
Downloading the Onboarding Preparation Sheet
We are preparing the Onboarding Preparation Sheet so that you can download it from this page within November 2026. Thank you for your patience.
Because your organization's decisions are kept in the sheet, the assumptions behind your operations can be handed over even when the person in charge changes. If a member of our Customer Success team is assigned to you, please send us your completed sheet. We use it to check your ramp-up progress and to contact you when needed.
Terms Used in This Guide#
These are terms that appear often in this guide. If you come across a term you don't know, come back here. More detailed explanations are available in the Glossary and the manual.
| Term | Meaning |
|---|---|
| Onboarding Preparation Sheet | A sheet that brings together, in one place, what to decide before onboarding (purpose, scope, team, and environment). You can get it from the download form |
| Group | The unit in which you register servers and respond to vulnerabilities. The scope you can see is also divided by group |
| Group set | A unit that combines multiple groups so you can see the overall status (CSIRT Plan) |
| Scanner | A small program that collects the list of software installed on a server and sends it to FutureVuls |
| Scan | Collecting the list of software and matching it against vulnerability information. Servers registered with a scanner are scanned automatically every day. For Paste Scan and SBOM servers on the Standard Plan, run a manual scan from the screen (Periodic Automatic Scans) |
| Task | A ticket for managing your response to "one vulnerability found on one server." Each task has an assignee, a due date, and a status |
| Status | The response status of a task. Statuses include New, Investigating, Ongoing, and Resolved |
| Important CVE | The list of vulnerabilities that your rules have sorted as "should be addressed" and that have not yet been addressed. This is what you check every day |
| SSVC | A way of classifying vulnerabilities into four levels based on "when to fix them." FutureVuls makes this decision automatically, taking your own environment into account (CSIRT Plan) |
| Immediate | The most urgent of the four SSVC levels, meaning "respond immediately." The others are Out-of-Cycle (respond outside the regular cycle), Scheduled (respond as planned), and Defer (postpone) |
| Vulnerability Priority / Task Priority | Priorities (such as high, medium, and low) that FutureVuls assigns to vulnerabilities and tasks. They are separate from the SSVC decision (Vulnerability Priority and Task Priority) |
| KEV | A catalog of vulnerabilities that are actually being exploited. Treat vulnerabilities listed in it as your top priority for response |
| CPE | A name tag that represents a product and its version in a globally standardized format. It is used to look up vulnerabilities in software installed outside of package management and in network devices |
| SBOM | Software Bill of Materials. A list of the software components included in a product or system |
Troubleshooting#
If something isn't working, see Troubleshooting (FAQ). If that doesn't solve the problem, contact us through the support contact form.
Next Page#
Next, go to "Quick Start: Try It on One Server." If you want to understand the overall process first, start with From Onboarding to Daily Operations.