Project & Development
Vulnerability Management Process: Asset Inventory, Priority, Fix Deadlines, and Exceptions
Advanced | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)
Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.
Vulnerability management works better when findings tie to an asset inventory, priority follows exploitation and impact, not score alone, and unfixable items become time-limited exceptions. It suits teams worn out by score-only ordering and IT or security staff building a process. Start by noting where the inventory lives and who owns it for servers, endpoints, network devices, and software. Then judge each finding on CISA's SSVC factors (exploitation, automatable, technical impact, mission and well-being impact) and set a target fix deadline for each outcome (Track, Track*, Attend, Act). Check internet exposure in the inventory, apart from SSVC. Check factor definitions in CISA's latest material. Inventory cross-checks and expired-exception reviews catch pitfalls early, such as chasing everything by score, missing devices, open-ended exceptions, and closing fixes unverified. The whiteboard has 4 pages and the task board 4 columns, with 4 parent tasks and 3 subtasks each.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Vulnerability Management Board
How to use (4 pages): ① On page 1, set purpose and scope and link the inventory and sources (boards①–⑤) → ② On page 2, set the 5-step flow and source owners (boards⑥⑦) → ③ On page 3, judge by SSVC factors, check pitfalls, set deadlines (boards⑧–⑫) → ④ On page 4, approve exceptions with an expiry, verify fixes, report monthly (boards⑬–⑮)
1/4 Link the inventory
① Purpose and Scope (start here)
- Purpose e.g. Fix actively exploited vulnerabilities first, and report to management once a month that they are fixed
- Scope e.g. Internal servers, employee endpoints, network devices at branches, and software used for work. Devices managed by partners are excluded
- Roles for judging and approving e.g. IT staff judge; the department head who owns the asset approves exceptions
② Inventory by Asset Type (location, owner, how you receive information, reachable from outside)
| Inventory location | Owner | How you receive information | Reachable from outside? | |
|---|---|---|---|---|
| Servers | e.g. The Servers sheet in the asset spreadsheet | e.g. Infrastructure team manager | e.g. Read the OS vendor's update notices weekly | e.g. The 2 public-facing servers are reachable |
| Endpoints | e.g. Device list in the endpoint management tool | e.g. Each department head | e.g. Update list in the management tool | e.g. Not reachable (internal network and VPN only) |
| Network devices | e.g. Device table per branch | e.g. Network team | e.g. Notices from the maintenance vendor | e.g. Perimeter devices are reachable |
| Software | e.g. Purchase and contract list | e.g. Owner in the using department | e.g. Notices on the vendor's official site | e.g. If unknown, write "TBC" |
③ Source: Product Vendors
- Security update notices issued by product vendors
- e.g. Open the OS and business software update pages from your bookmarks and check them
- Products to watch: ____ (write them from the products in inventory ②)
④ Source: Public Bodies
- Vulnerability information and advisories published by public bodies
- e.g. Check the list of vulnerabilities confirmed as exploited and match it against the products in inventory ②
- Confirm the name and location of the material to watch in the latest guidance, then write it down
⑤ Source: Vendors, Tools, Internal
- Notices from maintenance vendors, update lists in management tools, and reports from inside the company
- e.g. Accept vendor notices only when they come through the contract contact
- e.g. Route an employee report that an update notice is out to the record location
2/4 Draw the information flow
⑥ Five Steps from Inventory ② and Sources ③–⑤ to Closing One Finding
- Receive Record the information as one item in the record location e.g. Read the vendor notice, write the affected product and version, and find the matching asset in inventory ②
- Judge Decide the outcome with the factors on ⑧ e.g. Judge within 2 business days and write the outcome and the deadline from ⑫ in the record location
- Fix Apply the update or change the setting e.g. Agree on the owner and time, tell people about the business impact, then apply. If it cannot be fixed, go to ⑬
- Confirm in the record Check in the record that it was applied e.g. Align the update status, version, and management tool screen using the 4 steps of ⑭
- Report Summarize the count and exceptions e.g. Report to management and department heads once a month using the format in ⑮
⑦ Frequency, Owner, and Record Location per Source (rows are the sources in ③–⑤)
| Check frequency | Owner | Record location | Condition for judgment | |
|---|---|---|---|---|
| Vendor notices | e.g. Every Monday | e.g. Infrastructure team | e.g. Vulnerability response list | e.g. It matches a product and version in inventory ② |
| Public body information | e.g. Once a day | e.g. IT staff | e.g. Vulnerability response list | e.g. It is on the list of confirmed exploited vulnerabilities and matches a product in inventory ② |
| Maintenance vendor notices | e.g. When it arrives | e.g. Network team | e.g. Vulnerability response list | e.g. It came through the contract contact |
| Management tool lists | e.g. Every Wednesday | e.g. Endpoint team | e.g. Vulnerability response list | e.g. Some endpoints are still not updated |
| Internal reports | e.g. When it arrives | e.g. IT staff | e.g. Vulnerability response list | e.g. The asset was identified in inventory ② |
3/4 Set priority and deadlines
⑧ Judge on the SSVC Factors (use the one finding received in ⑥ and logged in the ⑦ record location)
| Values to choose from | Judgment for this finding | Where you confirmed it | |
|---|---|---|---|
| Exploitation status | None / Public proof of concept / Actively exploited | e.g. Reports of active exploitation | e.g. Vendor notice and public body advisory |
| Automatable | Yes / No (can it spread without human action?) | e.g. No (the notice says user action is required) | e.g. Vendor notice |
| Technical impact | Partial / Total | e.g. Total (the notice says the whole device can be controlled) | e.g. Vendor notice |
| Mission and well-being impact | Low / Medium / High (both mission and public well-being) | e.g. High (the ordering system would stop) | e.g. Confirmed with the owner in inventory ② |
⑨ Pitfall: Chasing Everything by Score
- What happens: e.g. Every finding is chased by score with the same deadline, so work on devices not reachable from outside eats up your time
- How to check: e.g. In the ⑮ report, look at the share of last month's work that was Act or Attend outcomes from ⑧
- Preventive step: e.g. Sort by the ⑧ outcome instead of the score, and bundle Track items into the monthly routine update
- Does it apply?: e.g. Yes. Last month we chased 30 items with the same deadline
⑩ Pitfall: Devices Missing from the Inventory
- What happens: e.g. A meeting-room device that is not in the inventory has never received an update
- How to check: e.g. Match the list of connected devices in the admin screen of a router or similar device against inventory ② by device name, and count devices not in the inventory
- Preventive step: e.g. Set a procedure to add a device to the inventory when you buy it or connect it to the internal network
- Does it apply?: e.g. No. The gap is 0 (check monthly)
⑪ Pitfall: Exceptions with No Expiry
- What happens: e.g. An exception approved a year ago is still in place after the approver moved on
- How to check: e.g. In the ⑬ exception register, count rows with no expiry and rows past their expiry
- Preventive step: e.g. Do not approve an exception without an expiry. When it expires, fix it or approve it again
- Does it apply?: e.g. Yes. 2 rows have no expiry
⑫ Fix Deadline per Outcome (apply to the ⑧ outcome; set the numbers yourself)
- Act (move now) e.g. Inform owners and managers, and also executives. Our target is within 3 business days. For an asset reachable from outside in ②, start the same day
- Attend (move soon) e.g. Our target is within 14 days. Inform the owner and manager, and set the day to fix
- Track and Track* (fix in the routine) e.g. Fix in the monthly routine update. For Track*, keep watching for new information until the next judgment day
4/4 Run exceptions and checks
⑬ Exception Register (items judged in ⑧ that cannot be fixed by the ⑫ deadline)
| Reason | Compensating control | Expiry | Approved by | |
|---|---|---|---|---|
| Exception 1 | e.g. Old device, and the vendor has issued no update | e.g. Move it to an internal network not reachable from outside and turn off unused functions | e.g. Until the device is replaced (end of the month, 3 months from now) | e.g. Department head of the network team |
| Exception 2 | e.g. The business software does not run on the new version | e.g. Limit who can use it and review the operation logs weekly | e.g. Until a supported version is released (review monthly) | e.g. Department head of the using department |
| Exception 3 | e.g. A manufacturing terminal that cannot be stopped | e.g. Separate the network and apply the update on the next planned shutdown day | e.g. The next planned shutdown day | e.g. Department head of manufacturing |
| Exception 4 | e.g. Write the reason | e.g. Write the compensating control | e.g. Do not approve a row with no expiry | e.g. Write who approved it |
⑭ Four Steps to Verify the Fix (pitfall: closing without verifying)
- Check update status Check the count in the update status e.g. In the management tool update status, see how many of the 30 target devices have received it
- Compare versions Compare the version record with the notice e.g. Compare the version record in the inventory with the fixed version in the vendor notice
- Check on screen Look at the management tool or device screen e.g. Check the version on the device admin screen and keep a screenshot at the record location
- Close and record Close only when all three agree What happens: e.g. Closing after only giving the instruction, leaving devices waiting for a restart How to check: e.g. See whether the records from the previous 3 steps are all there Preventive step: e.g. Do not close items that do not agree; go back to the fix step in ⑥
⑮ Monthly Report (write it from the ⑫ deadlines and ⑬ exceptions)
- Figures to report e.g. Act 2, Attend 5, past deadline 1, closed 18
- Exception review e.g. Of 3 exceptions that expired, 2 were fixed and 1 was approved again
- Inventory and pitfall check e.g. One device not in the inventory was found and registered. Report how ⑨ to ⑪ and ⑭ apply
Task board contents
Not started 16 items
Link the inventory
On page 1, set the purpose and scope of vulnerability management and link an inventory and information sources to each asset type. Once you know where each inventory lives and who owns it, the flow and judgments on the later pages can be tied to it. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.
Log asset owners
Open your current asset inventory (a spreadsheet or the device list in a management tool) and write only its location and owner on the four rows of board ② (servers, endpoints, network devices, software). Write "TBC" for anything unknown and it takes about 15 minutes.
Set purpose, scope
On board ①, write the purpose, the scope, and the roles for judging and approving. Also write what falls outside the scope (such as devices a partner manages), then move the card to Stakeholder review to finish.
Write 3 sources
On boards ③ to ⑤, write how you receive information from vendors, public bodies, and service providers or management tools, and which products in inventory ② each one covers. Owners are set on board ⑦. Done when nothing conflicts with the how-to-receive column of board ②.
Draw the info flow
On page 2, set the 5-step flow from receiving to reporting, and the frequency, owner, and record location for each source. Once it is clear who records what and where, the judgments on page 3 can be made on the same record.
Write the 5 steps
On the 5 steps of board ⑥, write what receive, judge, fix, confirm in the record, and report mean. Done when each step has an owner and a signal for handing over to the next step.
Set source owners
In the table on board ⑦, fill in the check frequency, owner, record location, and the condition for sending it to judgment for each of the 5 sources. Done when no row lacks an owner.
Pick one record log
If the record locations in board ⑦ are scattered, choose one place to keep a record per finding and rewrite them. Judgments and exceptions from page 3 on are kept in the record location you set here.
Priority & deadlines
On page 3, judge each finding on the SSVC factors, check the pitfalls, and set a fix deadline for each outcome. This is the core parent task, and the deadlines you set become the standard for exceptions and reports on page 4.
Judge 1 item (SSVC)
Pick one finding that you logged in the record location of board ⑦ at the receive step of board ⑥, and write the values for the four factors on board ⑧ and where you confirmed them. Look up the four-level outcome in CISA's latest decision guide. Done once it is in the record.
Check the pitfalls
For the three pitfalls on boards ⑨ to ⑪, rewrite what happens, how to check, the preventive step, and whether it applies, in your own words. Assign an owner to the preventive step for any that apply.
Set fix deadlines
On board ⑫, write the target fix deadline for Act, Attend, and Track/Track*, plus the conditions for moving it earlier for assets reachable from outside. Check the latest guidance for contract or industry requirements.
Exceptions & checks
On page 4, approve unfixable items as time-limited exceptions, verify fixes in 4 steps, and build a monthly report format. After the first report goes out, move the card to the In operation column of the task board.
Approve with expiry
In the table on board ⑬, write the reason, the compensating control, the expiry, and the approver for each item that cannot be fixed. Done when no row is missing an expiry.
Verify in 4 steps
Following the 4 steps of board ⑭, check the update status, the version record, and the management tool screen, and close only when all agree. Done when the first finding is closed.
Monthly report form
On board ⑮, write the monthly figures, the exception review, and the results of the inventory and pitfall checks. Done when you have set who receives the report and on which day.