Read your assessment report
Understand every section.
Use the evidence. Plan the fix.
A clear overview for management. Detailed findings for your technical team. Start with the six parts below, then look up any heading in the complete reference.
Start with the six parts of a finding.
- What we found
- The issue, affected systems, observed condition, category and known causes.
- Why it matters
- Consequences, likelihood and impact, with relevant business context.
- How risk is rated
- Technical severity, customer risk, rating rationale and CVSS where scored.
- How to fix it
- Recommended steps, category remediation playbooks and example fixes.
- The evidence
- Tools, reproduction commands, observed output, response samples and screenshots.
- References and mappings
- Technical guidance, CVE/CWE, OWASP Web Security Testing Guide and Top 10 references, plus ISO, SOC 2 and NIST mappings.
About the sample and conditional sections
Sections appear when relevant to the service, finding and available evidence. A field marked unknown, not recorded or not scored should be read with the assessment limits. The sample illustrates one finding; it does not contain every conditional section.
The same finding as the interactive sample
A file containing a GitHub token was publicly reachable.
The synthetic example is rated High. It explains the exposed file, the potential consequence, the evidence and the recommended response: remove the public file, revoke and rotate the exposed token, then retest the file’s accessibility. The sample contains no live credential; credential usability was not tested.
Complete report-heading reference
Choose a group to look up a heading. Each explanation remains available below, including fields that appear only when relevant to the assessment.
Report identity and sample status
- IntegrityLab.ai sample finding
- An illustration of how one finding is presented. This example concerns a self-owned, isolated lab and contains no live credential or customer data.
- Finding reference and headline
- The finding reference and a short description of the observed condition and its location. Use the reference to connect the summary, evidence and fix guidance for the same finding.
- variant
- The delivery version you are reading, such as customer or redacted. Different versions can include different evidence detail.
- generated
- When this report version was created. The sample says “Historical example”; it does not claim that a fresh assessment was run when you opened the page.
- Self-owned isolated lab illustration
- The example uses a controlled lab owned by the assessor. It is an explanation of the report format, rather than a customer assessment result.
- Historical example · current template
- The page places an older illustrative lab example in the current presentation. Its screenshot is historical evidence for the illustration.
- Report family
- Identifies the related set of report deliverables. Use it with the generation and run identifiers when comparing versions.
- Generation
- Identifies the particular report-generation instance. It helps distinguish a regenerated report from another copy in the same family.
- Run
- Identifies the assessment run associated with the report family. This is different from the time the report was generated.
- Redacted deliverable
- A delivery version with information removed under the delivery policy. The visible report indicates which evidence fields have been withheld.
- [Redacted for delivery]
- The field was deliberately withheld in this delivery version. This marker is not evidence that the command or output was absent from the assessment.
What was observed
- What we found
- The main condition recorded for this finding, stated in plain language. Read the observation and evidence alongside it to understand the support and limits.
- Observation
- Provides the fuller recorded description behind the headline. It can preserve details or qualifications that the short finding title cannot contain.
- Assessment boundary
- Explains a specific limit on what was assessed or verified. For exposed credentials, the sample states that discovered material is not used to authenticate or test account access.
- Credential assessment boundary
- The sample shows a credential-shaped lab placeholder. The assessor did not log in with it, test account access, or establish that it could be used.
- Why it matters
- Explains the possible consequence of the observed condition and why it deserves attention. Read it alongside the evidence, likelihood, impact and assessment limits; it does not mean the consequence was demonstrated through exploitation.
- Finding category
- Names the type of issue so that related findings and remediation guidance can be understood together.
- Secrets and credential exposure
- The category shown in this sample: credential material was returned without authentication. The category does not establish that a credential is live, valid, or usable.
- Known causes
- Lists conditions commonly associated with this type of issue. Use them as investigation leads; the list alone does not prove the exact cause in your environment.
- Grouped finding covering multiple endpoints
- One parent finding groups related observations. The parent headline is shared; each child entry identifies its own target and evidence.
- Protocol / equivalent variants
- Lists related protocol versions or equivalent variants under a grouped finding. The precise heading can vary with the finding; review each child target separately.
- Recorded observations
- Where applicable in the complete report, lists the child observations grouped under one finding, with their own references, targets, and available evidence.
- Target
- The asset or location associated with the finding. A target can be a host, endpoint, or URL; a target label alone does not prove public-internet reachability.
- Affected endpoints
- Lists the specific endpoints associated with the finding or child observation.
- Request URL
- Shows the exact URL associated with the recorded request when it differs from the broader target label.
- Observed at
- Records the observation time. It is a point-in-time record and may differ from the report-generation time.
- Tools
- Names the tools or inspection sources associated with the finding. It describes where the evidence came from; the tool name is not the risk rating.
- Additional Notes
- Provides recorded analyst comments that help explain the observation, uncertainty, or handling of the finding. Read them with any verification notice.
Risk and severity
- Customer risk
- The risk level used for the customer-facing finding. In the complete report it also drives the cover totals, summary table, and severity grouping.
- Source severity
- The severity supplied with the source finding. It is shown separately from customer risk because a source tool's label and the report's contextual result can differ.
- Technical assessment
- States the technical severity of the observed condition. It is separate from the customer's business context. A CVSS base score is shown only when the assessment calculated a supported vector.
- Contextual proposal
- Gives a qualitative rating proposed from the recorded client context. The methodology says this is not a complete OWASP Risk Rating factor calculation.
- Final result
- Shows the recorded analyst decision when one exists; otherwise it uses the contextual proposal. Read any decision or rating status alongside it. Unknown or unscored values remain explicit.
- Likelihood
- The assessment's qualitative view of how likely the concern is to lead to harm under the stated conditions. It is separate from the amount of harm and is not an EPSS probability.
- Impact
- The assessment's qualitative view of the potential consequence if the concern leads to harm. It does not by itself state how likely that outcome is.
- Severity rationale
- Explains why the recorded rating was chosen, including relevant evidence, assumptions, and limits. It is the place to look when a short High, Medium, or Low label needs context.
- CVSS
- Common Vulnerability Scoring System: a standardized way to describe vulnerability severity numerically. Where calculated, the report can show a score, a severity band, and a vector describing the scoring inputs. This sample is “Not scored”.
Official reference ↗ - Not scored
- No CVSS score is supplied for this finding. It does not mean a score of zero or no risk; the qualitative assessment and its rationale still apply.
- Client context
- Records the client-specific facts used to consider business risk, such as importance, sensitivity, and expected access. Missing context remains a limit on the assessment.
- Assessment perspective
- Describes the assessment viewpoint recorded in Client context. A viewpoint alone does not establish whether a system can be reached from the public internet.
- Business importance
- Where applicable within Client context, records how important the asset is to the business. A critical asset designation does not automatically make every finding Critical.
- Data sensitivity
- Where applicable within Client context, records the sensitivity classification used for the data. Read any accompanying note, including whether the value came from a default.
- Access expectation
- Where applicable within Client context, records who or what is expected to access the asset. Compare this with the observed behavior and the stated assessment boundary.
- Asset purpose
- Where applicable within Client context, explains the intended business or operational use of the asset.
- Business impact
- Where applicable within Client context, explains the recorded business consequence behind the contextual assessment.
- Context recorded by
- Identifies who recorded the client-context information. It is attribution for that context, rather than proof that every assumption was independently verified.
- Other client context recorded by
- Where applicable when data sensitivity uses a default, attributes the other recorded client-context information. Read the sensitivity note separately.
- Analyst justification
- Gives the recorded reason for the analyst's rating decision. It helps explain how the final result relates to the proposal and evidence.
- Policy basis
- Where applicable in an individual finding, identifies the rating policy or method recorded for the assessment. It explains the rating basis, rather than a compliance certification.
- Rating basis
- Where applicable in the complete report, states the recorded basis for the rating. Read it with the technical assessment, client context, and analyst justification.
- Lower rating
- Explains that the final result is below the contextual proposal and points to the analyst justification. A lower rating does not remove an uncertain observation or fill in missing client context.
- Threat-priority context
- Provides supplemental CVE-related KEV and EPSS information and any mapping limitations. These signals help prioritize follow-up; they do not change the recorded customer risk. An unavailable lookup is not a negative result.
Commands and text evidence
- Reproduction command
- Shows a recorded command associated with observing the condition. It helps an authorized asset owner understand the evidence request. The redacted example withholds the command.
- Observed output summary
- Shows a retained excerpt or summary of the tool output supporting the observation. It is a selected evidence view, rather than a promise that every raw output line is included.
- Response sample
- Separates returned response content from the assessor's interpretation. It may appear once for a finding or separately for child observations.
- (a) Returned content
- Shows the retained response text. The nearby notes can state that the sample is shortened or sensitive values have been removed.
- (b) Inspection conclusion
- Explains what the assessor concluded from the response. Read this separately from the returned text so the observation and interpretation remain clear.
- Assessor interpretation
- A label marking the inspection conclusion as interpretation. It is not text claimed to have been returned by the assessed service.
- No text sample is available.
- The response-sample view has no text sample to display. It does not establish that the service returned an empty body.
- Sample truncated.
- Only part of the returned content is shown. The visible excerpt should not be treated as the full response.
- Sensitive values redacted.
- Sensitive content was removed from the displayed sample under the delivery handling rules.
- No response sample was retained.
- No retained response sample is supplied for this inspection conclusion. It does not establish that no response was received.
- response bytes
- Gives the recorded response-body size. It can be larger than the text shown when the sample is shortened.
Fix guidance and references
- How to fix
- Recommended steps for addressing this finding. The asset owner should adapt the guidance to the environment and confirm the condition is resolved.
- Category remediation playbook
- Gives broader remediation actions for this type of issue. It supplements the finding-specific fix and can include prevention or follow-up checks.
- Example fix
- Provides illustrative code or configuration. It needs adaptation and validation for the actual stack; its presence does not mean a change has already been applied.
- Category reference resources
- Links to guidance about the broader finding category.
- Related attack paths
- Lists references to related modeled exposure paths for defensive analysis. A listed relationship does not by itself show that a chain was executed or that access was obtained.
- Technical references
- Links to documentation or guidance that helps explain the condition and its remediation. These are reference sources, separate from evidence captured during the assessment.
- Security references
- Groups identifiers and guidance used to classify or discuss the issue. A finding can lack some or all of these references.
- CVE
- Identifies a publicly disclosed vulnerability using a Common Vulnerabilities and Exposures reference. Configuration or access-control findings may have no applicable CVE; a missing identifier does not remove the finding.
Official reference ↗ - CWE
- Common Weakness Enumeration: a classification of a type of weakness. It describes the weakness category, rather than identifying one specific product vulnerability. The sample uses CWE-522 for insufficiently protected credentials.
Official reference ↗ - OWASP WSTG
- Points to the OWASP Web Security Testing Guide. A note may explain why a specific reference is absent. The reference is guidance, rather than proof that every test in the guide was performed.
Official reference ↗ - OWASP Top 10
- Relates the finding to an OWASP category of common web application security risks. The category is a way to discuss the issue, rather than a claim of full OWASP coverage.
Official reference ↗
Compliance references
- Compliance references
- Candidate control mappings for human review. The report explicitly says they do not establish compliance, certification, or an audit conclusion. A mapping is not finding-specific verification guidance.
- SOC 2 candidate references
- Candidate references for a human to consider in SOC 2 control work. They do not state that a SOC 2 examination was performed or that a control is effective.
Official reference ↗ - NIST CSF 2.0
- Candidate references to NIST Cybersecurity Framework 2.0 outcomes. They can help connect the finding with risk-management work; they are not a compliance pass or fail.
Official reference ↗ - NIST SP 800-53 Rev. 5
- Candidate references to NIST's catalog of security and privacy controls. Their relevance and implementation need human review.
Official reference ↗ - ISO/IEC 27001:2022 Annex A
- Candidate references to Annex A controls associated with the information-security management standard. The mapping does not establish certification or control effectiveness.
Official reference ↗
Screenshots, evidence sources, and integrity
- Evidence screenshot
- Provides an image supporting the recorded finding. The sample is a historical synthetic lab capture and has no live credential or customer data.
- Full-size capture
- Opens or expands the available screenshot for closer inspection.
- Capture hash
- Where supplied, a fingerprint for the capture file that can be compared with the original artifact. The sample explicitly says it is a historical illustration, not a current signed evidence hash.
- Finding evidence binding
- Where supplied, an integrity reference associating the finding with its recorded evidence. It is distinct from a reference URL or a risk score. This sample leaves the value blank, so no binding should be inferred from it.
- Screenshot render binding
- Where supplied, an integrity reference associating the displayed screenshot with its evidence context. It is distinct from the image's capture hash. The sample leaves this value blank.
- Raw evidence selector
- Where applicable in analyst delivery, identifies a location within the raw evidence for closer review. It is a pointer, rather than a second statement of severity.
- Primary source artifact
- Identifies the source evidence artifact and its recorded SHA-256 fingerprint. It helps locate and compare the source material behind the finding.
- Verification transcript
- Identifies a recorded verification transcript and its SHA-256 fingerprint. Read the transcript's scope and result; the label alone does not establish an outcome.
- Screenshot
- Where applicable for a grouped child in analyst delivery, identifies the child's screenshot artifact. The adjacent hash and render-binding values refer to that image and its evidence context.
- hash
- Where used beside a grouped child's screenshot, gives the recorded fingerprint of that screenshot artifact.
- render binding
- Where used beside a grouped child's screenshot, gives the reference connecting the rendered image to its evidence context.
- Low-severity screenshot policy
- Explains why a screenshot may be optional for this low-severity finding. Read the note and available text evidence; an omitted image alone does not establish that there was no finding.
- Evidence screenshot redacted
- The screenshot was removed under the delivery policy. This describes withholding, rather than saying that an image was never captured.
- No screenshot shown
- Explains why a screenshot is omitted. For example, an image may not visibly show the relevant proof even though the recorded tool output remains available.
- Evidence review status
- Records an evidence-review state such as needs_review or rejected. Treat that state as a qualification on the evidence, rather than silently assuming acceptance.
- Screenshot note
- Explains a screenshot-specific qualification or delivery note.
- Evidence screenshot withheld
- Explains that the screenshot is not included and provides the recorded reason or delivery-policy note.
Executive summary example
- Sample report · Basic+
- Identifies this as a sample report associated with the Basic+ presentation. The illustrated scope is still the one self-owned, isolated lab endpoint described below.
- Assessment scope
- States what this example covers. It prevents the one-endpoint illustration from being read as a broader assessment.
- Affected lab file
- Identifies the exact file location used by this self-owned, isolated lab illustration.
- Executive summary
- A short account of the recorded findings, their significance, and the main action to take. Use its linked finding for the detailed evidence and fix guidance.
- Remediation priorities
- Summarizes the recommended remediation focus and why it matters. Each priority can link back to the findings that support it.
- Example remediation priority
- The title of the sample remediation priority. It concerns exposed credential-shaped content in the lab; credential usability was not tested.
- Findings
- Links a summary statement or remediation priority to its supporting finding references.
- Assessment limits
- States the scope restrictions and uncertainties that qualify the summary. In this sample, only one self-owned, isolated lab endpoint is illustrated and no credential usability was tested.
Complete-report identity and navigation
- Client
- Names the client associated with this report.
- Assessment ID
- The identifier for the assessment engagement. It helps distinguish reports for different assessments.
- Report version
- The version recorded for this report. Compare it with the generated time and report-family identifiers when checking which copy you have.
- Generated
- When this report version was produced. It is separate from individual observation times.
- Service
- Names the selected assessment service or mode for the report. Read the scope and methodology for the actual work described.
- On this report
- Navigation links to the report's sections and individual findings.
- Back to top
- Returns to the beginning of the report.
- 1. Introduction
- Introduces the assessment and the report's automation or preparation notes.
- 1.1 Scope
- Describes the configured assessment targets and selected phases or integrated analysis. It defines the assessment boundary, rather than listing only locations with findings.
- Assessment scan phases
- Lists the assessment phases recorded for this report's scope.
- Integrated analysis modules
- Lists the analysis modules included in the report's scope description.
- In-scope URLs
- Lists or counts the configured assessment URLs. The full list can appear in Appendix C; the count is not a finding total.
- Host-only targets
- Lists targets recorded as hosts without a specific URL.
- 2. Executive summary
- The complete report's concise account of its customer findings and remediation priorities. Read the assessment limits and linked finding details alongside it.
- 3. Findings
- Contains the customer findings recorded in this report.
- 3.1 Findings summary
- A table for comparing findings by reference, headline, customer risk, available identifiers, and target.
- #
- The row number in the summary table. Use the Ref. ID to refer to the actual finding.
- Ref. ID
- The finding reference used to connect the summary row with the detailed finding.
- Title
- A short headline for the recorded finding.
- Risk
- The customer risk level used in the report's summary table. It is separate from a source tool's severity label.
- CVE / CWE
- Shows available vulnerability or weakness identifiers in the summary table. A dash means no identifier is shown in that row, rather than no finding.
- 3.2 Findings details
- Provides the recorded observation, risk context, evidence, references, and remediation guidance for each finding.
- No findings recorded.
- No customer findings are listed in this report. Interpret this with the stated scope, coverage gaps, and assessment limits; it does not establish that all assets or possible weaknesses were assessed.
- Appendix A — Severity legend
- Explains the report’s risk-level labels. The cover totals and detailed findings use the customer risk level.
- Appendix B — Methodology
- Explains the assessment phases or integrated analysis described by the report and the rating approach. It helps distinguish selected work, evidence, contextual judgments, and limitations.
- Risk rating
- Describes the report's evidence-qualified qualitative rating policy and how technical severity, client context, and analyst decisions remain distinct.
- Assessment phases actually executed or selected
- Where applicable in Methodology, lists the phases described for the assessment. Read the wording literally; a selected phase is not automatically a claim of successful completion.
- Integrated analysis
- Where applicable in Methodology, lists the integrated analysis included in the report description.
- Machine-readable export
- A structured data copy of the report that software can read. The report identifies this file as report.optrs.json.
- Appendix C — In-scope URLs
- Lists configured assessment URLs grouped by origin. It is the engagement scope list, rather than a list of affected locations.
- Appendix C
- A short navigation link to the complete in-scope URL list.
- Data handling note
- States the report's recorded retention schedule, scope, deletion timing or status, and any hold information. Read the actual dates and status instead of assuming that a scheduled deletion has already occurred.
Discovery evidence in the complete report
- Assessment discovery input
- The recorded starting input for assessment discovery. Discovery candidates are not automatically authorized assessment targets.
- Discovered candidates
- Counts candidate assets found through discovery and those promoted into engagement scope. Finding a candidate does not itself authorize assessment activity.
- Provider issues
- The number of recorded discovery-provider problems. These can limit the available discovery evidence.
- Items requiring analyst review
- An index of items needing interpretation or follow-up. Read Results by subject for the observations, context and recommended next steps.
- Distinct conclusions
- Counts the separate conclusions described by discovery evidence. It is different from the number of review concerns.
- review concerns
- Counts issues raised for analyst attention. Several concerns can relate to the same conclusion.
- Results by subject
- Organizes discovery results by the subject they concern and separates the observation, interpretation, source and time, and recommended next step.
- Unique conclusions
- The count of separate discovery conclusions, kept distinct from review concerns.
- Observed
- States the recorded facts within a discovery result.
- Meaning
- Explains the interpretation of those facts. Read it separately from the observation.
- Source / time
- Identifies the source and recorded observation time supporting the discovery result.
- Next
- States the suggested next step for the discovery result.
- Assessment passive DNS
- Presents retained DNS records supplied by the configured discovery provider. The section can instead state a coverage gap when no validated artifact was published.
- Provider
- Names the source provider recorded for the passive-DNS result.
- Zones
- Lists the DNS zones described by the passive-DNS collection.
- Suppressed out-of-scope records
- Counts records omitted because they were outside the configured scope.
- Name
- The DNS name associated with a retained passive-DNS record.
- Type
- The type of DNS record shown.
- Value
- The recorded value for that DNS record.
- Source
- The recorded source tool for the DNS record. This is evidence provenance, rather than a security rating.
- Coverage gap
- Explains a missing piece of expected evidence. For example, discovery may have been enabled without usable DNS evidence being retained. A coverage gap is not a clean result.
- Analyst-qualified scope intelligence
- Public records organized to help decide which systems belong in the assessment. Discovered names require review and approval before they become authorized testing targets.
- Analysis group
- The grouping used to organize retained scope-intelligence records.
- Retained records
- The number of records kept in that analysis group.
- Suppressed
- The number of records omitted from that analysis group.
Threat-intelligence source notes
- Threat intelligence context
- Supplemental information from CISA's Known Exploited Vulnerabilities catalog and FIRST's EPSS. KEV records known exploitation of a CVE; EPSS estimates the probability of exploitation of a published CVE in the wild over the next 30 days. Neither proves this asset was compromised, and the report says these signals do not change customer risk.
Official reference ↗ - Snapshot captured
- When the report's threat-intelligence snapshot was captured. It is a time-specific lookup rather than a live feed when the report is opened.
- CISA KEV source
- Identifies the KEV catalog source and the recorded retrieval status, with release or version information when available.
- FIRST EPSS source
- Identifies the EPSS source and its recorded retrieval status and data date when available.
- status
- In the threat-intelligence source note, states source availability or retrieval status. An unavailable status is not evidence that a CVE is absent from KEV or has a low EPSS score.
- released
- Where available in the KEV source note, states the recorded catalog release date.
- version
- Where available in the KEV source note, states the recorded catalog version.
- data date
- Where available in the EPSS source note, states the date of the EPSS data used.
Highlighted original evidence
- Highlighted original evidence
- Shows relevant excerpts from recorded tool output. Labels and highlights are IntegrityLab.ai annotations that help you locate the evidence.
- Highlighted original excerpt — page
- Identifies an excerpt page and, where available, its capture time. Page numbering organizes the retained excerpts; it does not indicate that the tool was rerun when the report was opened.
Missing or unassigned values
- Unknown
- The report does not supply a supported value for that field. Treat it as an explicit unknown rather than assuming a low rating or a clean result.
- Not applicable (access control / configuration finding)
- The report does not associate an applicable CVE with this finding. The observation and remediation guidance remain relevant.
- Not classified
- No CWE classification is supplied. This describes a missing classification, rather than absence of a recorded issue.
- Not recorded
- No value was recorded for that field in the report. It does not establish that the corresponding asset or event does not exist.
- —
- A summary-table placeholder indicating that no value is shown in that cell. Refer to the detailed finding and its assessment limits.
Headings that change with the report
- Report title
- The title identifies the assessment or report you are reading. Check it with the assessment ID, service and report version before using or sharing the results.
- Related variants heading
- Groups related versions or equivalent conditions under one finding. The heading can name the particular protocol or condition; review the target and evidence for each listed variant.
- Verification notice
- States a recorded verification result or qualification for a finding or individual observation. Read the notice and its explanation with the supporting evidence.
- Findings grouped by risk level
- Groups detailed findings by their assigned customer risk level so you can review higher-priority issues first.
- Severity-legend level
- Names a risk level and explains how the report uses it. Use the adjacent definition with the finding’s likelihood, impact and severity rationale.
- Discovery section heading
- Identifies the discovery work included in the assessment. The section separates names and systems found during discovery from the systems authorized for testing.
- Discovery subject
- Names the domain, host or other subject that the following discovery results describe.
- Discovery result heading
- Names an individual discovery result. The text beneath it records what was observed, what it may mean, its source and time, and the next step.
- Remediation priority title
- Names an issue to address in the executive summary. Follow its finding reference for the evidence and detailed fix guidance.
- URL origin and count
- Groups the approved assessment URLs by their shared scheme, hostname and port, and shows how many URLs are in each group. This is a scope list, not a finding count.
- Highlighted original excerpt page
- Identifies a page of the highlighted original evidence. A caption can also show when the evidence was captured.