Skip to content

Offensive Security

We verify the resilience of your systems - independently and methodically

We test web and mobile applications, APIs, network infrastructure, cloud environments and OT devices - methodically, based on OWASP, PTES and NIST SP 800-115.

Last updated: April 2026

Penetration Testing is a SEQRED service covering penetration testing of applications, apis, infrastructure, cloud and ot devices. cvss report, poc and retesting.

Offensive Security

Vulnerability scanners detect known flaws but don't test business logic, privilege escalation or vulnerability chains. IT teams need independent, manual verification - one that mirrors how a real attacker operates. Regular penetration testing delivers concrete evidence (PoC), CVSS prioritization and remediation recommendations that developers and administrators can act on immediately. It's also a starting point for meeting audit and regulatory requirements that increasingly demand documented security testing.

Scope

01

Web and mobile application testing (OWASP Top 10, ASVS)

02

API testing - REST, GraphQL, SOAP - authentication, authorization, business logic

03

Network infrastructure testing - internal and external

04

Cloud configuration testing (AWS, Azure, GCP)

05

OT/ICS device testing - firmware analysis, reverse engineering, protocol fuzzing

06

Wireless network security testing

07

Social engineering campaigns (phishing, vishing) as an entry vector

08

Retesting after remediation

Process

01

Scoping

We define the scope, methodology, and testing rules. We sign the Rules of Engagement.

02

Reconnaissance and analysis

We gather information about the attack surface - OSINT, scanning, fingerprinting.

03

Exploitation

Attempts to breach defences, including business logic testing and privilege escalation.

04

Reporting

A report describing vulnerabilities, proof of exploitation (PoC), and prioritised remediation recommendations using CVSS scoring.

05

Retesting

After remediation, we verify the effectiveness of the fixes.

FAQ

How often should we conduct penetration tests? +

We recommend at least once a year and after every significant change to your infrastructure or applications.

Can OT testing be safe for production environments? +

Yes - we use methodologies dedicated to industrial environments and agree with the client on permissible techniques before the engagement.

Which standards do you follow? +

We work based on OWASP Testing Guide, PTES, ISSAF, and - for OT - IEC 62443 and NIST SP 800-82 guidelines.

Will we receive help fixing the vulnerabilities found? +

The report includes detailed remediation recommendations. On request, we support the client's team during the implementation of fixes.

How does a pentest differ from vulnerability scanning? +

Scanning is the automated detection of known vulnerabilities. A pentest includes manual exploitation, business logic testing, and escalation attempts - providing a much more complete picture of risk.

How does SEQRED price its services? +

Pricing is based on an individual estimate of our consultants' time, considering the project scope and complexity. We present the offer broken down by phases - so you see exactly what you're paying for and can make decisions at each stage.

Can I speak with an expert before making a decision? +

Yes - an initial consultation is always welcome and free of charge. We help define the actual scope of your needs, which allows us to prepare a rational offer tailored to your organization.

What factors affect penetration testing costs? +

Key factors include the number of IP addresses, applications, and APIs to be tested, as well as the chosen testing model (black box, grey box, or white box). We also account for potential retesting after remediation.

We'll discuss scope, methodology, and timeline.

Book a consultation

Free consultation, no strings attached.