HOW WE WORK · DOCUMENTED METHODOLOGY & AUDIT TRAIL

The same four steps, every time, all on record.

Every engagement goes through the same steps, and your portal keeps a record of each one: what was in scope, how you proved the assets are yours, which commands an engineer approved, what held up under attack and whether each fix passed the retest.

EVERY STEP IS LOGGED
DNS-TXT Ownership ProofSigned Rules of EngagementHuman Operator GateCVSS v3.1 & MITRE ATT&CKVerified ControlsMandatory Retest
HUMAN-IN-THE-LOOP PROTOCOL
Operator Approved · Masked PoC · Retested
COMPLETE ENGAGEMENT RECORD
RoE · Commands · Findings · Verified Controls
https://dash.4tify.io/getting-started
DASH.4TIFY.IO // CLIENT WORKSPACE105 CATALOG CHECKS · 14 CATEGORIES
Onboarding·To fix (P1–P4)·Retest
ONBOARDING & 105-CHECK ASSESSMENTSTEP 01 – 02
01. Getting Started (5 Steps) & DNS-TXTAccount · Verify domain · Report · Team · Alerts
VERIFIED
02. 105 Catalog Checks (3 Tiers)45 Automated · 28 Semi-Automated · 32 Manual
100% VETTED
ANALYST_SUPPORTDEDICATED ANALYST · DIRECT CHAT
We test ourselves too
Grade A · 95/100
PORTAL QUEUE, 22P PDF & RETESTSTEP 03 – 04
03. PORTAL + 22P PDF · 04. MARKED FIXEDSYNCED 1:1
Live “To fix” Queue + 7-Section PDFBOTH INCLUDED
PASS / FAIL / REVIEWSLA: 7D / 14D / 60DRETEST: INCLUDED
01_getting_started_domain_verify5/5 READY
02_03_catalog_105_and_22p_report.pdf105/105
04_marked_fixed_retest_verifiedSCORE UPDATED
Onboarding done · domain verified by DNS-TXT

✓ Account secured · ✓ Domain verified · ✓ Team invited · ✓ Alerts set up · ✓ RoE signed

100%
Active testing only on assets you have proven are yours, inside the scope and hours you agreed
0
Raw scanner reports sent to you. An engineer reviews each finding before it is released
2×
Reports every time: a technical one for engineers (CVSS, proof) and a short one for management and customers
100%
Of findings are closed only after a retest shows they're fixed. Then we go through the results with you
ONE METHODOLOGY · TWO CADENCES

A one-off engagement or ongoing monitoring.

A penetration test before a release or a customer audit, or monitoring and recurring tests for 1 or 3 years. Both run in the same portal, under the same rules, with the same record.

Four steps, from written scope to a confirmed fix.

For a one-off penetration test or security audit: fixed scope, a known timeline, two reports and the retest included.

FIXED SCOPE · RETEST INCLUDED
STEP 01Day 1

Scope, DNS-TXT & RoE

We confirm you own the domain (DNS-TXT record or signed letter) and agree in writing the targets, exclusions, testing windows and emergency contacts.

Signed rules of engagement
STEP 02Days 2–8

Automated and manual testing

Automated passes an engineer has approved, plus manual testing of business logic, access control and APIs. We stop once a risk is proven.

Findings checked by an engineer
STEP 03Days 9–10

Two reports

A technical report for your engineers (CVSS, proof, how to fix) and a short summary for management (overall score, standards mapping, controls that held).

Technical and management PDFs
STEP 04Post-Patch

Retest and results call

Once your team has fixed things, we test every finding again, sign off the ones that are closed and go through the results with you on a call.

Retest results and sign-off
THE ENGAGEMENT ARC · FOUR STEPS, IN ORDER

What happens at each step and what is recorded on file.

We don't skip steps or run commands that haven't been approved, and a vulnerability stays open until we have tested it again.

01// OWNERSHIP & ROE SIGN-OFF

Scope and sign-off

Before we touch anything we agree in writing what we may test and how: targets, time windows, allowed techniques and an emergency contact on each side.

THE RULE
You prove the asset is yours with a DNS TXT record you add, or with a signed authorisation we keep on file.
  • Before any test, the domain is verified by a DNS-TXT record or we have your signed authorisation on file
  • The scope in writing: which hosts, at what hours, how fast, and which paths are off limits
  • A named technical and emergency contact on each side, and a way to pause testing at once
Step 01 // dash.4tify.io · Getting Started (5 of 5) & Scope Verification
1. Secure your account & 2. Verify your domainGuided onboarding in dash.4tify.io. No check runs until the domain is verified by DNS-TXT or the rules of engagement are signed
STEP 1 & 2 DONE
3. Get your first report & 4. Invite your teamYour assets in scope, riskiest first, each with a letter grade (e.g. C · api.acme-cloud.eu, B · portal.acme-cloud.eu, A · app.acme-cloud.eu)
STEP 3 & 4 DONE
5. Choose who gets alerts & Emergency ContactsChoose who is told about P1 critical issues, set the testing windows and name an emergency contact on each side
ONBOARDING 5/5
01 // Scope and sign-off
02// TESTING SUPERVISED BY AN ENGINEER

Test and assess

We work only inside what was agreed. Automated scans catch known problems. Our engineers look for flaws in logic and access control, and for small issues that combine into a bigger one, which scanners miss.

THE RULE
We stop once we can prove the problem and never go on to cause damage.
  • Automated passes find known CVEs and exposed services. Our engineers test logic, access control and how flaws chain together
  • We stop at the smallest masked sample that proves the risk. We don't pull databases
  • An engineer reviews every finding before it reaches you, so raw scanner output stays with us
Step 02 // 105 In-Scope Catalog Checks Across 14 Categories
Tier 1 · 45 / 45 Automated Checks (100%)
45 AutomatedOperator Approved

Catalog IDs VA-RCN-001..009, VA-INF-001..005, VA-WEB-CONF-001..004: OSINT, DNS/DNSSEC, TLS ciphers, HTTP headers, exposed DB/FTP ports & exploited CVEs

Tier 2 · 28 / 28 Semi-Automated Checks (100%)
28 Semi-AutoAnalyst Guided

Catalog IDs VA-WEB-CONF-005 (CORS), VA-WEB-ATHN, VA-API: analyst-guided configuration validation, session entropy, GraphQL/REST schema & rate-limiting checks

Tier 3 · 32 / 32 Manual Analyst Checks (100%)
32 ManualPASS / FAIL / REVIEW

Catalog IDs VA-WEB-ATHZ-001 (IDOR/BOLA), VA-WEB-BUSL-001..004 (business logic), VA-VAL-001..005 (chaining flaws and weeding out false positives; we stop once the risk is proven)

02 // Test and assess
03// TECHNICAL + EXECUTIVE + CONTROLS

Report, twice

A technical report for your engineers, with CVSS scores, evidence and steps to reproduce, and a short summary for the person who signs off the budget.

THE RULE
Every report has both parts, and also lists what we tested that came out fine.
  • Engineering report with CVSS v3.1 score, CWE, MITRE ATT&CK, request/response PoC and fix guide
  • A short summary for management, the board or a customer's procurement team
  • A 'Verified Controls' section lists what we tested that held up, which auditors ask for
Step 03 // Live Client Platform + 22-Page Confidential PDF Report
1. Live “To fix” Queue in dash.4tify.io (For Engineers)

Prioritized P1 Critical → P4 Low with SLA countdowns (7d / 14d / 30d / 60d), CLI/HTTP evidence and 1-click export

LIVE PORTAL + SLA
2. 22-Page Confidential PDF Report (7 Fixed Sections)

01 Executive Summary (A–F Security Score), 02 Scope (105 checks), 03 Findings, 04 Remediation Priority (with est. hours & due date), 05 OWASP/ATT&CK/CWE/NIST

7-SECTION PDF
3. Section 06 Assessment Coverage & 07 Signed Attestation

Every check in the catalog (VA-RCN, VA-INF, VA-WEB, VA-API, VA-SEC, VA-VAL, VA-RPT) logged as PASS, FAIL, REVIEW or NOT TESTED + Lead Operator sign-off

105/105 LOGGED
03 // Report, twice
04// VERIFIED RETEST & LIVE DEBRIEF

Retest and debrief

When you have fixed something, we test the same finding again and write down whether it is really closed. Then we go through the results on a call with your technical team.

THE RULE
We close a finding when the retest shows it's fixed. A ticket marked done isn't enough.
  • When your fix is live, we repeat the same attack and record the result
  • You get an updated report you can show regulators or customers
  • A call with your engineers to go through each finding and control
Step 04 // “Marked Fixed” Retest Workflow & Direct Analyst Support
Critical P1 · Multi-Tenant BOLA / IDOR on Invoices APIRETEST PASSED
Priority P1 · Open → Marked fixed in dash.4tify.io→ Developer patches authorization middleware and clicks 'Marked fixed' in portal → 4Tify re-verifies endpoint and closes P1
Direct Analyst Chat · Dedicated Security AnalystDIRECT ANALYST
Sidebar 'Message Analyst' · Live Remediation Guidance→ “Questions about a finding or what to fix first? Write to us any time.” You talk to the engineer who did the work, and we go through the results on a call.
Security Score Updated · Posture Grade A (95 / 100)SCORE UPDATED
Since your last assessment · Updated PDF Report Issued→ Dashboard gauge updates automatically (e.g., B 82/100 → A 95/100) and a fresh signed report is ready for download
04 // Retest and debrief
THE RULES WE HOLD OURSELVES TO

Why it is safe to let us in.

You're giving us access to your production systems and code. These four rules apply to every engagement, and the platform enforces them.

OPERATOR GATE

Active tests only on assets proven to be yours

Once you prove ownership through DNS, active tests run inside the scope and hours you agreed. Where ownership rests on a signed authorisation instead, an operator approves each active command before it is sent.

cmd_approval_policyhuman_operator_signature_required
REVIEW GATE

A person reviews results before you see them

Findings wait in a review queue until one of our team checks and releases them. Raw scanner output never reaches you directly.

finding_release_gatemanual_staff_verification_only
DATA MINIMISATION

We take as little data as the proof needs

We show a vulnerability with the smallest sample we can, and mask it. We don't download whole databases to make a point.

proof_of_concept_modeminimal_masked_sample · no_db_dump
FULL AUDIT TRAIL

Everything is on record

Scope, authorisation, every command we ran or had approved, every file we created and removed. You can show that record to an auditor.

immutable_engagement_logscope + commands + artefacts_cleaned
INSIDE THE CLIENT PLATFORM · DASH.4TIFY.IO

Where your team works with us day to day.

Reports don't get lost in email threads. Your team has its own workspace with a 5-step guided onboarding, an A–F grade for each asset, a prioritised 'To fix' list and a direct line to your analyst.

dash.4tify.io // Home · security score and assets (redacted demo)
WEEKLY POSTURE OVERVIEW
Good morning, Acme Team
1 critical issue needs your attention first. The rest can wait.
AC
Acme Cloud SRLRedacted Workspace
Your assets (Most at risk first)See all 6 →
C
api.acme-cloud.eu1 critical · 3 to fix
B
portal.acme-cloud.eu4 to fix
A
app.acme-cloud.eu2 to fix
A
auth.acme-cloud.eu2 to fix
Security scoreHow it works
B82/100
Good posture

Fixing the 1 critical issue on api.acme-cloud.eu takes your organization score to 94 (Grade A).

Getting started5 of 5
✓Secure your account
✓Verify your domain (_4tify-verify)
✓Get your first report
✓Invite your engineering team
✓Choose who gets P1 alerts
A
We test ourselves too4Tify scores 95/100 on the same 105-check assessment we run for you
See our results →
Assets, riskiest firstLIVE SCORE

Each domain and service gets a grade from A to F, and the portal shows how far your score would rise if you fixed the critical and high issues.

Your analyst, one click awayHUMAN SUPPORT

The card at the bottom left opens a conversation with the analyst assigned to you, for questions about a finding or about what to fix first.

We test ourselves too: 95/100GRADE A · 95

At the bottom of the dashboard you can open our own results (A, 95/100) on the same 105 checks we run for you.

STRUCTURED EVIDENCE SCHEMA

What you get for each finding: ten fields, always filled in.

The platform won't release a finding unless it has a CVSS vector, evidence and a specific recommendation on how to fix it.

Finding Ingest Schema · 10 Mandatory Fields (Never Empty)
severitycritical / high / medium / low / info
cvss_scoreCVSS v3.1, 0.0–10.0
affected_componentthe exact host, endpoint or file
evidencerequest / response or output that proves it
owaspOWASP Top 10 category
cweCWE identifier
mitre_attackATT&CK technique
nist_csfNIST CSF function
cveconfirmed by a tool, or marked unconfirmed
recommendationwhat to change, specifically
Sample Verified Finding · Portal & PDF Output
FINDING #FND-2026-014STATUS: RETEST PASSED
{ "severity": "critical", "cvss_score": "9.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N)", "affected_component": "GET /api/v2/orgs/:org_id/invoices", "owasp": "API1:2023 - Broken Object Level Authorization", "cwe": "CWE-639: Authorization Bypass Through User-Controlled Key", "mitre_attack": "T1078 - Valid Accounts / Cross-Tenant Access", "nist_csf": "PR.AC-4 (Access Permissions & Authorizations)", "evidence": "Masked HTTP request/response proving Tenant A read 1 record of Tenant B", "recommendation": "Bind organization scope strictly to server-verified JWT claim" }
Built to scale

Pricing that fits.

Start with a single scan. Add testing and monitoring when you need them, or put several services together for 1 or 3 years.

Free exposure report

See what attackers see, free.

Tell us your domain and we'll check what anyone can see from outside: leaked logins, email security, certificates and exposed services. You get a short summary within 48 hours.

Public data onlyWe never test your systems48-hour turnaround
Get my free report No credit card. No commitment.

Vulnerability scan

A full scan of your website or app, with a clear report of what's exposed and how to fix it.

€49.50/ asset€55Winter Sales · −10%
  • Single scan + retest€55€49.50
  • Monitored, monthly€80€72 / month
  • Monitored, weekly€200€180 / month
  • Monitored, daily€500€450 / month
  • Findings ranked by risk, with fixes
  • Monitoring: recurring scans and alerts
Get started
Most requested

Penetration test

Our engineers attack your app the way a real attacker would, and back every finding with proof.

from€1,350one-off€1,500Winter Sales · −10%
  • Web application€1,500€1,350
  • Mobile application€2,000€1,800
  • Web + mobile€3,000€2,700
  • Hands-on testing by our engineers
  • Every finding proven with evidence
Book a penetration test

Dark web monitoring

We watch the deep and dark web for your company's names, domains and leaked credentials.

€22.50/ keyword / month€25Winter Sales · −10%
  • 10 monitored keywords€250€225 / month
  • Leaked credentials and data for sale
  • Mentions of your brand and domains
  • Checked once a month, with an alert for anything new
Start monitoring

All-in-one

Need several of these? We put them in one proposal for 1 or 3 years, with a discount for the longer commitment.

1- or 3-year discount
Pick any of these
  • Vulnerability scanning & monitoring
  • Penetration testing
  • Dark web monitoring
  • Bug hunting
  • Attack surface management
  • Signal (closed beta)
Talk to an expert

Open source & non-profit

If you maintain an open-source project or run a non-profit, we can cover you for free or at a reduced price. Just write to us.

Learn more

Prices exclude VAT. The scope is confirmed with you before we start.