Tessera Start a check IT

Quick Check methodology

What the scan runs, with which tools, how we calculate CVSS scores and the security score, and what is left out.

Last updated: · Hyperion S.r.l.

In short

The Tessera Quick Check is an automated, external scan without credentials that runs four checks in sequence: HTTP security headers, TLS configuration with testssl.sh, known vulnerabilities with Nuclei and an application scan with OWASP ZAP. Every issue gets a CVSS v3.1 score calculated with FIRST's official formula and a risk level derived from that score. The report always states what was not tested.

Before the scan: authorisation and destinations

The four checks

CheckToolWhat it verifies
Security headersDirect HTTP requestPresence of Content-Security-Policy, Strict-Transport-Security, X-Frame-Options and X-Content-Type-Options; reports the X-Powered-By header.
TLS configurationtestssl.sh (fast mode)Protocols offered (SSLv2 to TLS 1.3), cipher categories, certificate chain, expiry, known TLS vulnerabilities (Heartbleed, ROBOT, POODLE, SWEET32, FREAK, DROWN, LUCKY13 and others).
Known vulnerabilitiesNuclei 3.0.4Templates for exposed files, misconfigurations, default credentials and technology fingerprinting, with medium, high or critical severity. Limited to 150 requests per second.
Application scanOWASP ZAP 2.17.0Spider (up to 90 seconds), passive scan and active scan capped at 120 seconds: if the cap is reached, the report states that coverage is partial.

How we calculate CVSS

The score is calculated with the official CVSS v3.1 formula published by FIRST, not estimated. The source of the vector depends on the tool:

Some of the vectors we use for ZAP alerts:

AlertCVSS v3.1 vectorScore
Strict-Transport-Security Header Not SetCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N4.8
Missing Anti-clickjacking HeaderCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N4.3
Content Security Policy (CSP) Header Not SetCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N4.2
Server Leaks Information via "X-Powered-By"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N3.7
HTTPS Content Available via HTTPCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N3.7
Cookie without SameSite AttributeCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N3.1
X-Content-Type-Options Header MissingCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N3.1
Cookie No HttpOnly FlagCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N3.1

Risk levels

High, Medium and Low are derived from the CVSS score, not from the tool's label, so label and score can never contradict each other:

LevelCVSS scoreMeaning
High7.0 to 10.0Exploitable issue with serious impact: requires urgent action.
Medium4.0 to 6.9Exploitable under specific conditions or a significant control weakness: to be fixed in the short term.
Low0.1 to 3.9Hardening or defence-in-depth gap: to be addressed during normal maintenance.
Informationalnot applicableObservation with no direct impact, included for completeness.

Security score

At the top, the report sums up the result as a score from 0 to 100 and a grade. The calculation uses only the findings in the report:

GradeScoreRating
A90 to 100Excellent
B75 to 89Good
C60 to 74Fair
D40 to 59Needs work
F0 to 39Critical

For example, a site with four Low issues and no High or Medium ones scores 88 (grade B); a site with a single High issue cannot exceed 49 (grade D). The score is a summary: what to fix is decided by the individual findings and recommendations.

Summary and recommendations

The summary and prioritised recommendations are written by Claude (Anthropic) based only on the findings already determined by the tools: the model does not decide severities and does not add findings. In English reports the tools' original descriptions are kept as they are. If the service is unavailable, the report uses fixed texts and says so.

What it does not cover

This is why the Quick Check is not a penetration test: see the differences between a penetration test and an automated scan.

Reference standards

The report uses CVSS v3.1 and MITRE's CWE classification. Its structure (summary, scope and rules of engagement, methodology, findings, recommendations, appendices) follows the Penetration Testing Execution Standard and NIST SP 800-115; the OWASP Web Security Testing Guide is the reference for the areas actually covered.

Data and retention

Reports open with a signed link valid for 7 days and are deleted after 90 days. Details are in the privacy notice. A complete report on a fictitious site is available as a sample report.