Preview
This guide is a preview. Its content may change.
Planning 1: Define Your Goals#
For Everyone
To make sure FutureVuls doesn't end up as something you "just installed," start by agreeing internally on what you will use it for and what success looks like. Record your decisions in the Onboarding Preparation Sheet. The Onboarding Preparation Sheet brings together in one place everything you should decide before onboarding (goals, scope, team, and environment), and you can get it from the download form. If you have a contract, your starter kit also includes a download link. We expect the person who will lead day-to-day operations to fill it out.
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.
Why Decide First#
Without a clear goal, you may feel you have to address every vulnerability, and the sheer number can stop you in your tracks. On the other hand, if your goal is clear, such as "We want to be able to explain our status in audits" or "We want to stop missing vulnerabilities," it becomes clear which vulnerabilities to start with and how far to go.
Five Things to Decide#
| # | What to decide | Examples | Where to record it in the Onboarding Preparation Sheet |
|---|---|---|---|
| 1 | The challenges you want to solve | "Reduce the effort spent on vulnerability response," "Eliminate missed responses and dependence on specific individuals," "Comply with audits and regulations," "Report status to senior management," and so on. You can choose more than one | Challenges to solve (B-1) |
| 2 | Deadline-driven events | If there are dates you need to work back from, such as an internal audit or a report to a committee, write them down | Deadline-driven events and target dates (B-3, B-12) |
| 3 | The scope you will register first (initial scope) | Decide the number of servers and the departments you will register in the first two months. Example: "50 servers in the IT department" | Scope to register first |
| 4 | The scope you will eventually expand to | Decide how far you will ultimately expand during the contract period. If this hasn't been decided yet, enter your contracted number of servers as a placeholder and update it once it's decided | Scope to eventually expand to |
| 5 | What "operations are running smoothly" means | Examples: "No backlog of vulnerabilities that need immediate action" or "No more than ◯ unaddressed vulnerabilities per server." Also write a one-line picture of what success looks like six months from now | State of smooth operations and six-month picture (B-18, B-19) |
You Don't Need to Roll Out Company-Wide from the Start#
The initial scope is a starting point for establishing how you will operate. If you register all of your company's servers at once, the number of detected vulnerabilities grows large, and you are likely to get stuck before you have decided how to sort them. We recommend completing the three ramp-up stages within the initial scope first, then expanding from there.
What to Do After Deciding#
- Record your decisions in the Onboarding Preparation Sheet.
- Share the contents with stakeholders in your organization (managers, contacts in each department, and so on) and get their agreement.
- If you have an assigned Customer Success representative from our team, send them the Onboarding Preparation Sheet.
Troubleshooting#
If something isn't working, see Troubleshooting (FAQ).
If you're unsure how to decide, contact us through the support contact form.
Next Page#
Next, decide who sees what. Continue to Planning 2: Decide Your Team and Visibility.