ALMETECK — Penetration Testing & Offensive Security Consultancy
Penetration testing & offensive security

Find the failure point before someone else does.

ALMETECK tests your systems the way an engineer tests a structure — methodically, under real conditions, with every finding documented well enough to act on. No scanner dump. No vague risk score. Just what's broken and how to fix it.

SCOPE OF TESTING
Web Applications Networks Cloud APIs Wireless Social Engineering
How an engagement runs

A fixed methodology, applied every time.

01

Recon

Passive and active reconnaissance to map your exposed footprint before touching anything in scope.

02

Enumeration

Identify live services, versions and entry points across the agreed target scope.

03

Exploitation

Attempt real exploitation of what we found — safely, and only inside the rules of engagement.

04

Post-exploitation

Assess actual impact: what an attacker could reach, escalate to, or pull out from there.

05

Reporting

A prioritized report — what's broken, how it was broken, and exactly how to fix it.

Services

Testing scoped to how your systems actually work.

WEB

Web Application Testing

OWASP-aligned assessment of your applications for injection, broken auth and business-logic flaws.

NETWORK

Network & Infrastructure

External and internal testing to map every exploitable path across your perimeter and internal network.

CLOUD

Cloud Security Assessment

Configuration review and exploitation testing across AWS, Azure and GCP environments.

API

API Security Testing

REST and GraphQL testing for broken authorization, injection and unintended data exposure.

HUMAN

Social Engineering

Phishing and pretexting exercises that test your organization's human attack surface.

RED TEAM

Red Team Engagements

Objective-based, multi-vector engagements that simulate how a real adversary would operate.

Why it's built this way

An engineer's discipline, applied to security.

Most security testing gets sold as a scan with a PDF stapled to it. We treat an engagement the way you'd treat a structural assessment: define the scope precisely, test under real conditions, and document every finding so the person who has to fix it doesn't have to guess what we meant.

That means reproducible steps, real evidence, and remediation guidance that's specific to your stack — not a generic checklist copied across every client.

Scoped
EVERY ENGAGEMENT WRITTEN & AGREED UP FRONT
Reproducible
FINDINGS INCLUDE STEPS & EVIDENCE
Prioritized
RANKED BY REAL IMPACT, NOT CVSS ALONE
Actionable
REMEDIATION WRITTEN FOR YOUR STACK
What you receive

Every finding, in the same clear format.

FINDING-014 · API-GATEWAY-01 CRITICAL

Unauthenticated access to internal auth endpoint

DESCRIPTION
The reverse proxy forwards requests to /internal/auth/verify without validating a session token, allowing any external client to reach an endpoint intended for internal service-to-service calls only.
IMPACT
An attacker can enumerate valid sessions and impersonate authenticated users without credentials.
REMEDIATION
Restrict the route to internal network ranges at the proxy layer and require service-to-service authentication in addition to network restrictions.
Get in touch

Ready to find your weak point?

Tell us what you need tested and roughly when. We'll come back with a scoped proposal — not a sales call.