Why Instance Grade Scores May Be Missing at the Start of a New Reporting Period

Last updated: December 23, 2025

At the beginning of a new reporting period, instance grade scores in Cyrisma may appear as a dash (–) or be temporarily unavailable. This behavior is expected and is related to how reporting periods are calculated and displayed within the platform.

This article explains why this occurs and how to ensure grade scores are populated as expected.

How Reporting Periods Work in Cyrisma

Cyrisma calculates risk grades and scoring metrics based on scan data collected within the current reporting period.

Reporting periods are defined as follows:

  • Monthly reporting periods begin on the first day of each month and end on the last day of that month.

  • Quarterly reporting periods begin on:

    • January 1

    • April 1

    • July 1

    • October 1

At the start of a new month or quarter, the platform does not carry forward scan results from the previous period.

Why Grade Scores Appear Missing

If no scans have been completed during the current reporting period, Cyrisma has no data to calculate grade scores. As a result:

  • Scores may appear as a dash (–)

  • Certain dashboard metrics may be temporarily blank

This does not indicate a platform issue or a loss of historical data. It simply means new scan data has not yet been collected for the current period.

Best Practice to Avoid Gaps in Visibility

To ensure grade scores are available early in each reporting period:

  • Run vulnerability, baseline, or relevant scans within the first few days of the new month or quarter

  • Maintain regular scanning schedules that align with reporting cycles

Completing scans early ensures dashboards and reports populate promptly with up-to-date risk and compliance data.

Key Notes

  • Historical scores from previous periods remain available in reporting views

  • Grade scores update automatically once new scans complete

  • No manual action is required beyond running scans in the new period

Summary

Missing instance grade scores at the start of a new reporting period are expected behavior in Cyrisma. Scores populate only after scans run within the current month or quarter. Scheduling scans early in each reporting cycle ensures continuous visibility into your environment’s risk posture.