Product security support-period tracker

What does the product security support-period tracker produce?

Compare declared product-version support commitments with actual customer-reported support events and expose premature discontinuation.

Enter the approved scopes, rule versions and dates listed below. Review complete calendar findings and keep the recoverable backup before preparing the finalized pack.

What do you need before you start?

• Define the authorized source population and your review rules.
• Record each exact scope, approved source version, deadline basis and calendar exclusion.
• Review missing and invalid inputs before preparing the finalized pack.

What information do you enter?

Enter the task-specific calendar fields below. No legal dates, holiday calendar or source authority is inferred.

• Calendar or review reference. Customer-controlled reference.
• Calendar version. Customer-controlled version.
• Calendar owner. Responsible customer owner.
• Review date or exact instant. YYYY-MM-DD for date-only items. Exact timestamp with seconds and a confirmed UTC offset for hour rules. Mixed date and hour calendars require an exact instant.
• Selected review scope. Declare the population and intended jurisdiction/activity coverage. No completeness is inferred.
• Product-version support commitments. JSON array, at most 200 rows. Exact text keys. itemId, product, version, startsOn, endsOn, owner, approvedBy, approvedOn, source. Unknown fields are rejected.
• Actual reported support events. JSON array, at most 200 rows. Exact text keys. eventId, itemId, on, action, evidence. Unknown fields are rejected.

What you can download

Every result must identify its supplied facts, assumptions and unresolved items.

Fictional review report (PDF). Editable review (DOCX). Complete fictional pack (ZIP). Requires tailoring and responsible review. Samples use the finalized renderer.

How does the product security support-period tracker work?

1. 1
   Define the approved calendar

   Calendar or review reference. Customer-controlled reference.

2. 2
   Freeze the review rules

   Validate approved product/version commitments and their start/end chronology. Order linked support events within the selected review instant. Compare the latest reported support state with each active commitment. Missing observations and premature discontinuation remain unresolved.

3. 3
   Inspect complete findings

   Review all source-linked results and unresolved items. Free JSON and CSV preserve complete results.

4. 4
   Keep recoverable work

   Exact input strings save locally and survive reload. Validate a tool-specific backup before replacing current work. A prior checkpoint and earlier generic records remain preserved separately. Recalculate after restoring.

5. 5
   Prepare the finalized pack

   Prepare eight complete files, including private ICS events, then download them free. Review the fictional sample below.

Method and sources

Apply the steps above to the supported inputs. Use the listed source sections to review the rule basis, assumptions and limits.

• Internet Calendaring and Scheduling Core Object SpecificationiCalendar text escaping and line folding, date-only events, UTC instants and noninclusive event ends. This format reference supplies no legal deadlines or holiday calendar. Sections 3.1, 3.3.4, 3.3.5 and 3.6.1.Internet Engineering Task Force. Reviewed 2026-10-09.

Common questions

What still needs review?

Dates and scopes come from your declarations. No statutory rule, approval authority, receipt definition, source currency, business calendar or permission is inferred. No filing, notice, reminder delivery, external provider call or scheduled cloud check occurs. Inputs and history stay in this browser. Original files are not saved to the cloud.

JSON tables support 200 rows each and 20000 characters per answer. Formal reports display the first 100 findings, at most 1000 characters per preview. Excel, CSV and JSON preserve every accepted finding.

Calendar days count from day zero. Calendar months clamp to the final valid day. Business days use Saturdays, Sundays and only the explicitly selected excluded dates. These are calculation assumptions, not legal interpretations.

Elapsed hours use exact UTC instants, not wall-clock or daylight-saving adjustments. ICS files do not schedule delivery or synchronize an external account.

Related working records

The related workspace contains working administrative records. Open it for the related administrative task.

Related tools

Browse all cybersecurity tools.

• CMMC evidence readiness packPrepare the currently applicable scope and supporting records. Try a free example. Review your inputs and result. No account or payment required.
• NIST 800-171 implementation workbookUse the correct version for the customer’s actual requirement. Try a free example. Review your inputs and result. No account or payment required.
• SSP and POA&M assemblerDraft from verified boundaries, controls and deficiencies. Try a free example. Review your inputs and result. No account or payment required.
• FedRAMP documentation preparationOrganize supplied evidence without implying authorization. Try a free example. Review your inputs and result. No account or payment required.
• PCI DSS evidence preparationSupport the selected assessment route without issuing an attestation. Try a free example. Review your inputs and result.