OPC UA security modes in practice
None, Sign or SignAndEncrypt: what an attacker sees in each mode, and which configuration we recommend.
Offensive security testing from web applications through Active Directory to industrial control systems. You receive the findings on our client platform, where you can also track remediation, and we keep monitoring your external attack surface between engagements.
Hands-on, manual testing. Automated tools are only a starting point; every finding is validated.
Written authorization, and a passive approach in industrial environments. Operational safety comes before every test.
Public methodology and a fee agreed in advance.
Beyond finding the issues, we prepare your team so they do not happen again.
Web application, API, mobile and AI/LLM testing across every role, including business logic.
External and internal pentests, assumed breach, and a documented attack path to Domain Admin.
Configuration review of Entra ID, Exchange Online, SharePoint, Azure and AWS, including privilege escalation paths.
Passive OT assessment without disrupting production, PLC and OPC UA review, IEC 62443 segmentation.
Weekly external scanning, alerts on new assets and critical findings, quarterly management report.
Supplier quick assessment, 90-day remediation plan, awareness and OT training, executive workshop.
Findings appear on the MFA-protected client platform while testing is still in progress. There you can track remediation, request retests and export tasks to Jira. At the end of the project you receive a closure letter that you can share with partners or your auditor.
PLC modules, an OPC UA aggregator, an industrial network and a simulated manufacturing execution environment. Every technique is validated in our own lab first.
A reconnaissance pipeline, honeypot infrastructure and a PTaaS platform. We automate repetitive steps so expert time goes into real analysis.
OWASP, MITRE ATT&CK, IEC 62443, NIST SP 800-82. Our testing methodology is public.
A call and a questionnaire, followed by a written fixed-fee proposal.
NDA, contract, exact scope and testing window.
Live findings on the platform and immediate notice of any critical issue.
Executive and technical sections, after quality review.
Verification of the fixes, followed by a closure letter.
None, Sign or SignAndEncrypt: what an attacker sees in each mode, and which configuration we recommend.
Unauthenticated remote code execution in every web-facing PHP deployment. Who is affected, what to do, what to look for in the logs.
What NIS2-regulated partners ask, and the mistakes we see most often in the answers.
Briefly describe the system you would like tested and the reason for the engagement: a partner or regulatory requirement, an audit, or a new system going live. We will get back to you within one business day.