History Refresh: How Infrastructure Changes Impact Historical Ratings Ingrid A History Refresh is a process applied when structural changes are made to a company's profile that have a historical impact on its findings, risk vector grades, and overall rating.This process ensures that historical data accurately reflects the company's structure at that specific point in time, and that findings are correctly attributed based on asset start and end dates.Why is a History Refresh Triggered?A History Refresh is typically required when updates alter a company's digital footprint. Common triggers include:Infrastructure Remapping: Adding, deleting, relocating, or end-dating assets.Corporate Restructuring: Connecting or disconnecting subsidiaries from a parent company.New Documentation: Processing newly created self-published reports.Note: Because accurate historical data depends on these updates, a History Refresh is an essential part of almost every infrastructure change or correction requested through Support.What to Expect During a History RefreshDuring a refresh, the BitSight platform completely rebuilds and recaptures the company’s list of findings from the ground up. Because both your infrastructure and the BitSight platform's detection capabilities evolve over time, this rebuilding process may result in:New Findings: You may see brand-new findings appear both currently and historically. This happens because the platform is evaluating past infrastructure against updated detection logic.Rating and Grade Fluctuations: This comprehensive rebuild will likely reflect changes in your current and historical overall ratings, as well as specific risk vector grades.Opt Out of a History RefreshIf you do not want a History Refresh to occur, you must explicitly state this when submitting your request to Support.Important Caveat: Opting out of a History Refresh prevents us from applying changes retroactively. This significantly limits the types of infrastructure corrections and updates Support can perform on your company profile.May 19, 2026: Article expanded.August 13, 2024: Published. Related articles Sovereign API Endpoint Subsidiary Attribution TLS/SSL Finding Remediation & Remediation Verification Updating IP Registration Web Application Header Finding Messages Feedback 0 comments Please sign in to leave a comment.