Testing & Attack Simulation
Penetration testing of applications, networks, cloud and PLCs
We test web and mobile applications, APIs, network infrastructure, cloud environments and OT devices. Every finding includes proof of exploitation (PoC), a CVSS 4.0 score and actionable remediation steps.
- 5
- 8+
Testing & Attack Simulation
- Web and mobile applications
- APIs (REST, GraphQL, SOAP)
- Network infrastructure
Vulnerability scanners detect known flaws but miss business logic errors, privilege escalation paths and vulnerability chains. A scanner report lists the flaws it found and does not say what an attacker could achieve with them. Security teams need independent, manual verification that mirrors how an attacker operates: authentication bypass, network pivoting, configuration exploitation. Each test ends with proof of exploitation (PoC) for every vulnerability, a CVSS 4.0 score and a remediation recommendation that developers can act on immediately. The report documents the testing of systems and the assessment of the effectiveness of measures that NIS2 Art. 21(2)(e) and (f), DORA Articles 24 and 25, PCI DSS 4.0.1 requirement 11.4 and ISO/IEC 27001:2022 controls A.8.8 and A.8.29 call for.
Scope of the service
Web and mobile applications - OWASP Top 10, ASVS, business logic, authorization, session management
APIs (REST, GraphQL, SOAP) - OWASP API Security Top 10 2023: authentication, object-level and function-level authorization, rate limiting, input validation
Network infrastructure - external attack surface, internal pivoting, Active Directory
Cloud configuration (AWS, Azure, GCP) - IAM, storage, network segmentation, CIS benchmarks
OT/ICS devices and protocols (Modbus, OPC UA, DNP3, IEC 61850, PROFINET) - firmware analysis, protocol reverse engineering and fuzzing only on test, spare or replicated devices; on the production network only passive techniques and agreed low-risk tests, preferably during a planned outage
Wireless networks - Wi-Fi (WPA2/3), Bluetooth, IoT protocols
Social engineering - phishing, vishing, pretexting as an entry vector
Retesting after remediation - verification report ready for auditors
How we work, step by step
Scoping
We agree the scope, objectives and testing model (black, grey or white box) and, before the start, sign the Rules of Engagement.
Reconnaissance and analysis
We gather information about the attack surface: OSINT, port and service scanning, technology fingerprinting and application mapping.
Exploitation
Attempts to breach defences: exploiting vulnerabilities, privilege escalation, lateral movement through the network and business logic testing.
Reporting
Report with vulnerability descriptions, proof of exploitation (PoC), a CVSS 4.0 score, standards mapping (OWASP, CWE) and actionable remediation steps.
Retesting
After remediation, we verify that fixes are effective. The retest report confirms closure - ready for your auditor.
Results for our clients
Leading entity in the Polish energy sector
CSIRE System API Security Testing
Penetration tests of the portals, applications and B2B APIs of Poland's Central Energy Market Information System to OWASP ASVS, a configuration review and a comparison of production with the test environment.
View projectIdentity and Access Management System Testing
Critical infrastructure organization of strategic importance to national security
IT and OT Device Security Testing
Industrial device vendors and operators (mining, energy, automation)
Security audit of an energy operator's OT technology network
Critical energy infrastructure operator
What the test report contains
The report has two layers: a summary for management and a description of every vulnerability for the team that will fix it. This is how it is laid out.
- Management summary
- The summary states what we tested, which risks are most serious and where to start fixing, in language that needs no technical background.
- Scope and rules of the test
- This part lists the systems in scope, the test model (black, grey or white box) and the rules of engagement signed before the start.
- Each vulnerability described
- Each vulnerability has a description, proof of exploitation (PoC), a CVSS 4.0 score and mapping to OWASP and CWE.
- Recommendation and owner
- Each vulnerability has a specific fix and a suggested owner on the client side, so the ticket goes straight to the right team.
- Order of fixes
- The order of fixes combines the CVSS 4.0 score with the importance of the system to your business.
- Mapping to requirements
- Results are mapped to NIS2 Art. 21, PCI DSS 4.0.1 requirement 11.4 and ISO/IEC 27001 control A.8.8.
- Retest report
- Once fixes are in place, the retest report confirms which vulnerabilities are closed. You hand this document to your auditor as evidence of remediation.
Who we serve
We've worked with national energy grid operators, systemically important banks, industrial automation manufacturers, renewable energy operators, and US DoD contractors.
Not sure this service fits your situation? Describe your environment and deadline in a few lines and we will propose a scope. We reply within one business day.
Frequently asked questions
How often should we conduct penetration tests?
At least once a year and after every significant infrastructure or application change. PCI DSS 4.0.1 requires a penetration test at least every 12 months and after a significant change (requirements 11.4.2 and 11.4.3), and DORA requires financial entities other than microenterprises to test all systems that support critical or important functions at least yearly (Article 24(6)). NIS2 requires testing of systems and a way to assess the effectiveness of measures (Article 21(2)(e) and (f)) but sets no frequency. For CI/CD development, a test after each major release is usual.
How does a pentest differ from vulnerability scanning?
Scanning automatically detects known vulnerabilities from a signature database. A pentest includes manual exploitation, business logic testing, privilege escalation and chaining vulnerabilities into attack paths. A scanner finds a missing patch - a pentester shows what an attacker can do with it.
What is the difference between black box, grey box and white box?
Black box - the tester has no prior knowledge and simulates an external attacker. Grey box - the tester has partial knowledge (for example a user account or API documentation), which gives the best ratio of cost to coverage. White box - full access to source code and documentation for the deepest analysis.
Which standards do you follow?
We test web applications to OWASP WSTG and ASVS 5.0, mobile applications to OWASP MASTG and MASVS, and infrastructure to PTES and NIST SP 800-115. In OT environments we follow the safe-testing guidance of NIST SP 800-82 Rev. 3 and relate findings to the requirements of IEC 62443-3-3 for systems and IEC 62443-4-2 for components.
Can OT testing be safe for production environments?
We limit the risk as follows: in the production network we use passive reconnaissance and traffic analysis without interference, and we run fuzzing and active tests only on test or spare devices or within a maintenance window. We agree every technique with you before we start.
What does the report include?
Executive summary, each vulnerability with proof of exploitation (PoC), CVSS scoring, standards mapping (OWASP, CWE), prioritization and remediation steps with a suggested owner on your side. After retesting - confirmation that vulnerabilities are closed.
Is the report enough for a NIS2 or PCI DSS audit?
It is one of the pieces of evidence auditors expect. We map findings to NIS2 Article 21, PCI DSS 4.0.1 (Requirement 11.4) and ISO/IEC 27001 (A.8.8), and the retest report confirms remediation. A penetration test does not replace a compliance audit, which also covers processes, policies and risk management.
How is a penetration test priced?
We estimate how many tester days the scope needs: the number of IP addresses, applications and APIs, the test model (black, grey or white box) and the complexity of the environment. We multiply the days by the daily rate and break the offer down by stage, so the retest after fixes appears as a separate item. We help you define the scope on a free call.
How long does a typical penetration test take?
Depends on scope. A web application test typically takes 5-10 working days. Network infrastructure 3-7 days. We deliver the report within a week of completing tests. Retesting is scheduled after remediation.
What certifications do your testers hold?
Our team includes specialists holding OSCP, OSWE and OSCE (Offensive Security), BSCP (Burp Suite) and CISSP certifications. OT testing is led by specialists with industrial protocol experience and GICSP, GRID and ISA/IEC 62443 Cybersecurity Expert certifications. We list the certifications of every consultant assigned to your project in the proposal.
Related sectors, services and insights
Sectors
- Banking and financeWe test a bank's digital channels and run red teaming aligned with the TIBER-EU methodology.
- EnergyWe check whether the operational network can be reached from the IT network or over VPN.
- DefenseWe combine CMMC and NIS2 requirements into a single work plan for your company.
- Manufacturing and industryWe secure older automation too, and plan tests together with your maintenance team.
Services
- Red TeamingWe test whether your defence team detects and stops a multi-stage attack on your organisation.
- DORA ComplianceWe build the register of information on ICT contracts and the major incident classification.
- NIS2 Compliance AuditWe establish whether NIS2 applies to you and which security measures are still missing.
Articles
- Anonymity on the Internet - what the fall of criminal services teaches and how to protect privacy lawfullyHow law enforcement de-anonymised users of forums and markets on Tor, what follows for organisations, and how to protect privacy in line with Tor Project guidance.
- DDoS Attacks on Industrial Infrastructure - Threats and ProtectionDDoS attacks on OT/ICS systems - vectors, incidents (Killnet, NoName057), critical infrastructure protection, and NIS2 requirements.
- Local administrator accounts in ICS - protection against pass-the-hash and credential theftProtecting local administrator accounts in ICS: LAPS, pass-the-hash, default HMI and PLC passwords, Active Directory hardening in OT. Checklist and IEC 62443-3-3 basis.
We'll discuss scope, methodology, and timeline.
Free consultation, no strings attached.








