Skip to content
After Kenna

PROGRAM GUIDE, read 10 Nov 2026

Start 12 months before the date that binds you, and count back in four blocks

All guidesGlossary

Find the date that binds you

For Cisco Vulnerability Management customers the dates come from bulletin EOL15812: end-of-sale 10 Mar 2026, end of service contract renewal 11 Jun 2026 and Last Date of Support 30 Jun 2028. Your own term end can be earlier. Take the earlier of the two as the deadline.

For Vulcan Cyber customers the binding date is in your contract with Tenable or with Vulcan before it, not in a public notice. Tenable closed the acquisition on 7 Feb 2025. For a Brinqa customer whose fit has changed, the renewal date is your date; Brinqa is on sale and announced the acquisition of PlexTrac on 19 Aug 2026, so there is no lifecycle deadline. For a spreadsheet, the date is the audit or the staff change that makes it unsafe.

Four blocks

Plan backward from the binding date with these blocks. The durations are planning allowances based on program practice, not vendor statements; adjust them to your team size.

A fifth item sits outside the blocks: the notice period in your current contract. Many contracts set a notice period for non-renewal ahead of the term end. Read yours.

BlockAllowanceWhat ends it
Selection2 to 3 monthsSigned order or written decision
Build3 to 4 monthsAll sources connected, rules rebuilt, history loaded
Parallel run2 to 3 monthsExit rule met
Cutover and wind down1 monthOld tickets and exports archived

A worked example

Take a team whose Cisco term ends 30 Jun 2028. A 12 month plan starts on 30 Jun 2027. Selection runs July to September 2027. Build runs October 2027 to January 2028. Parallel running runs February to April 2028. Cutover and wind down take May 2028, leaving June as buffer.

Now take a team that is already late. As of 10 Nov 2026, a team with a term ending 31 Dec 2026 has about seven weeks. It cannot run the blocks. It should export everything now (see the export guide), choose the shortest viable path, and negotiate a short extension in writing. The bulletin states a Last Date of Support of 30 Jun 2028 but your order controls what you receive.

Negotiate with the clock

Procurement takes longer than people expect. Ask each candidate vendor for a pilot with your data in the selection block, and ask for pricing in writing. Nucleus publishes no pricing (quote only), and Brinqa's pricing page returned an error when we read it on 2026-11-10, so build quote time into the plan.

Ask your current vendor for a short extension. A short extension at term end can cover a parallel run. Do this before the term end, and ask for any export help to be named in the same document.

  • Write down the earlier of your term end and 30 Jun 2028.
  • Check your contract's notice period for non-renewal.
  • Put pilot dates in the vendor's proposal.
  • Keep a month of buffer after cutover.

Signals that the plan is slipping

Watch for four signals. The first is a selection block that has run past three months without a signed pilot. The second is a build block in which fewer than half of the sources are connected at the midpoint. The third is a parallel run that starts without an exit rule. The fourth is a decision about history that is still open when the build starts.

Each signal has a standard response. Cut the selection list to two candidates. Connect the three largest sources first and leave the rest for the parallel run. Write the exit rule in a single message and get the director to approve it. Make the history decision using the three tiers in the guide on choosing what history to bring.

Report progress to the director on one page: the binding date, the block you are in, the days left, the next decision and the owner of that decision. A page with those five items beats a long status deck, and it makes slippage visible while there is still time to cut scope.

The same arithmetic holds for any vendor. Whether the binding date is a Cisco Last Date of Support, a Tenable contract term or a Brinqa renewal, count the months, subtract the four blocks, and write the start date at the top of the plan. If the start date is already behind you, the plan is a recovery plan, and it should say which block is being shortened and what risk that creates.

Give the director the date on which the plan becomes a recovery plan. It is usually earlier than the team expects, and naming it early keeps the choice between scope and time with the people who can make it.

Sources

  1. Cisco bulletin EOL15812, read 10 Nov 2026
  2. Tenable: completes acquisition of Vulcan Cyber, read 10 Nov 2026
  3. Brinqa: acquires PlexTrac (19 Aug 2026), read 10 Nov 2026

Last reviewed 10 Nov 2026.