CSV Export
Purpose
This article explains what the CSV Export feature is for, what kind of information it is intended to export, and how it can be used outside the plugin. The goal is to help administrators understand CSV export as a practical way to move CMSSPM data into spreadsheets, reporting workflows, or other review processes.
Where to find it
CSV export is typically used from reporting, findings, history, or dashboard-related views where tabular data is available. It is intended for administrators who want to work with the plugin’s data outside the WordPress interface.
What CSV export includes
A CSV export is a flat, spreadsheet-friendly version of selected plugin data. Depending on the view and feature scope, exported data may include information such as:
- findings and their statuses,
- category or section names,
- scan timestamps,
- scoring-related values,
- notes or metadata associated with findings,
- mitigation state where applicable.
The exact columns can vary depending on what is being exported, but the main purpose is to provide structured data that can be filtered, sorted, archived, or shared more easily.
Why CSV export is useful
CSV export is useful when you need to review results outside the plugin interface. Common uses include:
- opening results in Excel, Google Sheets, or LibreOffice Calc,
- sharing findings with other teams,
- building internal reports or audit workpapers,
- comparing results across scans,
- preserving a snapshot of findings at a point in time.
This is especially helpful when someone needs the data itself, not just the on-screen dashboard summary.
How mitigation appears in exports
When findings have been marked as mitigated, that state should be reflected in the export along with the related finding information. Depending on the export format, this may include the mitigation status, the note or justification, and the user associated with applying the mitigation.
This is important because a mitigated finding is treated as passing for scoring purposes, but it still remains part of the recorded history. Including that state in the export helps preserve the difference between a finding that passed naturally and one that was formally mitigated.
How to use exported data
A practical workflow for CSV export is:
- Review findings or scan data inside CMSSPM.
- Export the relevant dataset to CSV.
- Open it in your spreadsheet or reporting tool.
- Sort, filter, or compare the rows as needed.
- Use the exported snapshot for documentation, coordination, or further analysis.
Because CSV is simple and widely supported, it works well as a bridge between the plugin and other operational workflows.
Notes and scope
This article is a general overview of the CSV export feature. It does not define the exact export schema, every available column, or how different views may format their exports.
Those details should be documented separately if you want field-level documentation for administrators, auditors, or developers. This page is intended to explain the purpose of CSV export and what users should expect from it.