CL / 002 2026
Expertise / Cylantro Labs
Technical security assessments shaped by the system.
We begin by understanding the architecture and the question that needs answering. The scope, access and method follow from there.
Architecture → access → method
Assessment areas
Where we work.
Applications and code
When software handles different users, sensitive data or complex workflows, the question is how its behavior and implementation hold up under attack.
Web applications
Test business logic, access controls, authentication, sessions and input handling. Black-, grey- or white-box access follows the project.
APIs
Examine REST and SOAP interfaces, authorization, data handling, encryption and communication channels between systems.
Desktop applications
Assess installed clients, their local resources, server communication, configuration and access controls.
Mobile applications
Examine iOS and Android apps, local storage, network communication, authentication and third-party libraries.
Source code review
Use automated static analysis and manual white-box review to find weaknesses in the implementation itself.
Infrastructure, cloud and networks
When services are exposed, connected or divided into zones, we test where access is possible and whether the intended boundaries work.
Infrastructure
Assess servers, operating systems, running services, configuration and permissions; typically from a black-box starting point.
AWS cloud
Review IAM permissions, network rules, encryption and storage settings across the AWS environment.
Internal networks
Start from a compromised employee workstation to assess discovery, privilege escalation, movement between systems and AD weaknesses.
Network security
Examine network devices, firewalls, VPNs, access rules and traffic between segments.
Network segregation
Test both directions across VLANs, subnets and security zones to see whether firewall and routing rules enforce separation.
Devices and wireless
When a product joins hardware, firmware, radio and remote services, an isolated software check can miss the path between them.
IoT devices
Assess firmware, diagnostic ports, device authentication, communication, encryption and remote access.
Routers and modems
Examine firmware and hardware, web administration, Wi-Fi settings and exposed network services.
Wi-Fi networks
Test configuration, encryption, authentication and access points, including simulated interception and rogue access points.
Vulnerability research and exploit development
Some systems call for focused research to uncover weaknesses and verify their actual impact. We take on this work through individually agreed engagements.
Vulnerability research
Targeted examination of a specific system, component or technology to identify previously unknown vulnerabilities.
Exploit development
Purpose-built proof-of-concept exploits to demonstrate the practical impact of a vulnerability under controlled conditions.
People and workstations
When a realistic entry point is an employee or their computer, the assessment looks at both the attempt to gain access and what that access permits.
Phishing and social engineering
Simulate email, phone and fake-website approaches to measure responses and identify gaps in security controls.
Workstations
Check local privileges, access, policies, configuration and restrictions on connected devices such as USB.
Coordinated attack simulations
When the question concerns detection and response across a whole organisation, separate component tests give only part of the answer.
Red teaming
Coordinate attacks across networks, applications, people and processes; the scope can be shaped for DORA TLPT or TIBER-EU engagements.
For unusual or hard-to-classify challenges, we start with the system and shape the assessment around it.
Describe the taskOur approach
A useful answer needs context.
The findings should explain what a weakness means for this system and where to act.
- 01 Understand the system
- 02 Design the assessment
- 03 Explain the findings
Start with the question