Skip to content
NewVerdictIQ Connector is here. One Docker image enriches your DNS logs with verdicts inside your network and forwards them to your SIEM.Install guide

Basic Security Hardening

It indicates the presence of baseline hardening signals such as standard security headers (e.g., HSTS, X-Content-Type-Options, X-Frame-Options) and safer cookie flags (Secure/HttpOnly) used in a consistent but not fully strict manner.

Also surfaces as:
Strong Security HardeningEnterprise Grade Security Hardening
Analyst Q&A

What this signal answers

The questions every analyst asks before acting on this signal.

What it detects01

What does 'Security Hardening' indicate?

It indicates the presence of baseline hardening signals such as standard security headers (e.g., HSTS, X-Content-Type-Options, X-Frame-Options) and safer cookie flags (Secure/HttpOnly) used in a consistent but not fully strict manner.

Why it matters02

What does 'Enterprise Grade Security Hardening' mean?

It describes a mature, enterprise-style security posture where security headers, TLS enforcement, cookie policies, and CORS behavior are consistently hardened and policy-aligned, typical of well-managed production environments.

How analysts use it03

How should SOC analysts interpret this label?

This is a safe-leaning context signal: it reduces suspicion for generic web threats and lowers the likelihood of commodity phishing kits. It should not override strong malicious indicators, but it can strengthen confidence when other safe signals also exist.

Evidence shape

What Basic Security Hardening looks like in the response

A realistic shape of the entry the engine appends to the risk_signals array when this signal fires. Evidence keys are subgroup-default; per-signal overrides documented in the API reference.

json
{
  "slug": "security_hardening_profile",
  "name": "Basic Security Hardening",
  "group": "http_crawling_history",
  "subgroup": "http_header_behaviors",
  "direction": "safe",
  "evidence": {
    "missing_security_headers": 4,
    "cors_origin": "*",
    "cors_credentials_allowed": true,
    "provider_type": "self_hosted",
    "risky_cookie_count": 2
  }
}
See in API reference
Siblings

Peers in HTTP Header Behaviors

12 other signals share the same subgroup. They detect related behaviors and often co-fire on the same IOC.

Standard Session Cookie Stack

The response sets session cookies that belong to mainstream web application frameworks, such as JSESSIONID, PHPSESSID or…

Safe
Suspicious CORS Exposure

It indicates weak or overly permissive CORS configurations such as wildcard origins, broad method or header allowances, …

MaliciousCore
Suspicious Header Structure

It indicates abnormal HTTP header structures such as unusually minimal or dense header sets, odd ordering, unexpected pr…

MaliciousCore
Basic Profiling Cookie Risk

It indicates that the site sets cookies issued by specific edge protection providers whose cookies appear far more often…

MaliciousCore
Show 8 more in HTTP Header Behaviors
In the wild

See Basic Security Hardening fire on real IOCs

The Verdict Gallery is a curated stream of real verdicts. Filter by this signal to see exactly which IOCs it caught, what other signals fired alongside it, and what the engine recommended.

Open Verdict Gallery
Pre-filtered to Basic Security Hardening. See real IOCs this signal caught and the verdicts the engine returned.
Verdicts ✓

Start free, in five minutes

1,000 verdicts/month on the free tier, LLM layer included. No card required.