Review the analysis results
Read the summary, detected standards and findings of an analyzed report, filter them and accept or discard each finding.
On this page
When an analysis is Completed, its details show what the AI found in the report. Your job is to review it: confirm what applies, discard what doesn't and turn what needs fixing into action plans.
Before you start
Any role can view the results.
To accept, discard or reopen findings you need the Administrator or Editor role.
The report list
In Operations → External reports, each row shows:
Column | What it shows |
|---|---|
Report | The name, the file and its size. |
Type | Ethical hacking, Pentest, Audit, SOC report, Vulnerability scan or Other. |
Status | Processing, Completed or Error (with the reason). |
Findings | How many there are of each severity, for example 2 Critical, 5 High. |
Standards detected | The codes of the standards the report touches. |
Uploaded | Date, time and who uploaded it. |
Open the details
Press the row or the eye icon (View details). At the top you'll see the date and who uploaded it.
If the analysis is still in progress, you'll see The AI is reading the report. The view updates automatically when it finishes.
If it failed, you'll see The report could not be analyzed with the reason. See Analyze an external report.
Summary
A paragraph on what the report is, its scope and its main conclusion. If the report was analyzed in parts, it includes one paragraph per part; if it was too long to analyze in full, it starts with a Warning: notice that says how far it was read (see Analyze an external report).
Standards detected
Each standard appears with its code and its relevance to the report (high, medium or low). Hover over a standard to see why it applies.
Code | Standard |
|---|---|
ISO27001 | ISO/IEC 27001 |
ISO22301 | ISO 22301, business continuity |
LEYMARCO | Law 21.663 (Chile's Cybersecurity Framework Law) |
NISTCSF | NIST Cybersecurity Framework 2.0 |
PDP | Law 21.719 (Chile's Personal Data Protection Law) |
If the report mentions another law or framework that SofIA Governance doesn't cover yet, it appears in yellow with Not in catalog. If none was detected, you'll see The AI did not identify any applicable standards.
Anonymization
Which data was replaced before the analysis and the record of the accepted terms. See What is anonymized before the analysis.
Findings
The title shows how many findings you see out of the total, for example Findings (5/12). Each finding includes:
Its severity and its status.
The description and the Recommendation:.
Assets: the affected hosts or addresses, with their real values.
Controls: the framework controls the AI related to it, for example 8.8 Management of technical vulnerabilities. Hover over a control to see why it is related.
Once accepted: its code (for example, HAL-0031), its classification and the see in Findings and nonconformities link. If it was linked to controls or requirements, instead of Controls: you'll see ISMS controls: and Requirements: (the standard and the requirement code).
Action plan:, one for each plan you created, with a link to Action plans.
SofIA Governance only shows controls that exist in the framework. If the AI proposes a code that doesn't exist, it is discarded. If a finding has no controls, link them yourself after accepting it, from Findings and nonconformities.
Filter the findings
Above the findings list you have two filters:
All severities: Critical, High, Medium or Low.
All statuses: Pending, Accepted, In treatment, In verification, Closed or Discarded.
If none match, you'll see No findings match the filters. If the report had no findings, you'll see The AI found no findings in this report.
Review each finding
All findings start as Pending: they are AI proposals. In Audit and improvement → Findings and nonconformities they don't appear in the normal view; you only see them if you filter by Unreviewed proposal, and from there the Review in External reports button brings you back to this screen. Below each finding you have:
Accept: you confirm the finding applies to your company. In Accept finding you choose its Classification (it starts at Technical finding; also Major nonconformity, Minor nonconformity, Observation or Improvement opportunity) and press Accept. It changes to Accepted and is linked:
to the controls in your ISMS with the codes the AI read;
to the requirements of your adopted standards that those controls cover;
to the assets whose name, code, hostname or IP match those in the report.
Discard: the finding doesn't apply, is a false positive or was already resolved. It changes to Discarded and appears dimmed. An accepted finding can also be discarded as long as it has no action plan.
Reopen: appears on discarded findings and returns them to Pending.
Create action plan: appears on accepted and in-treatment findings. See Create an action plan from a finding.
You'll see Finding accepted., Finding discarded. or Finding reopened. as appropriate.
Once you accept it, the finding follows the lifecycle of any ISMS finding (correction, root cause, plan and effectiveness verification) in Findings and nonconformities. There, the Accepted status is called Open.
Start by filtering Critical and High with Pending status: those are the ones best decided first.
If something goes wrong
Message | What to do |
|---|---|
The finding has an action plan: it cannot be discarded. | A finding with a plan is already under treatment. Follow its lifecycle in Findings and nonconformities. |
The finding is already under treatment: follow its lifecycle in Findings and nonconformities. | Someone else already moved the finding forward. Close the details, open them again and continue from Findings and nonconformities. |