Led by a founder with more than 21 years of experience

contact@guilda.io

Cybersecurity

Penetration testing services and red team operations

We test your applications, networks, cloud and identity systems the way an attacker would, and red team operations go after a goal you set. Every engagement ends with a findings report and a retest of what your team has fixed.

Overview

A penetration test answers a simple question: if someone tried to break in, what would they get? We answer it by trying, within limits you set and with your written authorisation, and then by showing you exactly what we found and how to close it. The work covers six areas, from a single web application to an operation that tests your whole organisation.

Penetration testing

A penetration test looks for as many weaknesses as possible in a defined scope. We test web applications and APIs, external and internal networks, cloud configurations and mobile applications. Web and API testing follows the OWASP testing approach, so the coverage is familiar to your developers and to anyone reviewing the report. A typical test takes two to six weeks and is fixed price.

Red team operations

A red team operation works toward one goal you choose, such as reaching a payment system or the data of a particular team, by any route an attacker could take. It runs for four to eight weeks and emulates a real adversary, which makes it a test of how your people and processes notice and respond, not only of the technology. It suits companies that already test regularly and want to know whether their defences hold up as a whole.

Identity and Active Directory security

Many serious attacks pass through identity at some point. Active Directory testing looks for the paths that let an attacker move from an ordinary account to full control of the domain: weak delegation, stale privileges, exposed credentials and misconfigured trust. The result is a list of paths and the changes that remove them.

Cloud, web and API security

Applications rarely run alone. Cloud configuration testing reviews the AWS, Microsoft Azure or Google Cloud accounts behind them for exposed storage, excessive permissions and management interfaces open to the internet. Combined with web and API testing, it shows how a weakness in the application and a gap in the account behind it could add up.

Purple team exercises

A purple team exercise is a working session rather than a test. We run attacker techniques aligned with MITRE ATT&CK while your defenders watch their tools, and together we check whether each technique was detected. Where it was not, the gap is closed on the spot or added to a list of rules to write. Exercises take two to six weeks and are fixed price, and they pair well with our SIEM implementation work.

Remediation and retesting

Every engagement ends the same way. You receive a findings report, we walk your technical team through it, and once your team has made the fixes, we retest each finding and update the report. The retest is part of the engagement, not an extra, because a list of problems is only useful when you can show which ones are closed. If you want help with the network and server fixes themselves, Network & Systems Security covers them, scoped separately so the retest stays independent.

Deliverables

What you get

  • Web application and API testing

    Manual testing of your web applications and APIs against the OWASP testing approach, covering authentication, access control, input handling, business logic and how the application exposes data.

  • Network testing, external and internal

    External testing of what anyone on the internet can reach, and internal testing from the position of an attacker who already has a foothold, such as a compromised laptop.

  • Cloud configuration testing

    A review of your AWS, Microsoft Azure or Google Cloud accounts for the misconfigurations attackers look for first, such as exposed storage, excessive permissions and open management interfaces.

  • Mobile application testing

    Testing of your iOS or Android application and the APIs behind it, including how it stores data on the device and how it talks to your servers.

  • Identity and Active Directory testing

    Testing of Active Directory and your identity setup for the paths attackers use to move from one account to full control, such as weak delegation, stale privileges and exposed credentials.

  • Red team operations

    Adversary emulation and objective-based attack simulations over four to eight weeks, aimed at a goal you choose, such as reaching a payment system, to test your people and processes as well as your technology.

  • Purple team exercises

    Working sessions in which we run attacker techniques aligned with MITRE ATT&CK while your defenders watch, so that each gap in detection is found and closed together.

  • Findings report and retest

    A written report of every finding, with the evidence and how to fix it, followed by a retest once your team has made the fixes, so you know which issues are closed.

Process

How an engagement runs

  1. Agree the scope and the rules

    We agree what is in scope, what is not, the testing window, who to call if something breaks and how findings that cannot wait are reported. Nothing is tested without written authorisation.

  2. Map the target

    We study what is in scope the way an attacker would, from public information to the application's own behaviour, and plan the tests around what we find.

  3. Test

    2 to 6 weeks

    We test by hand, using tools where they help but not relying on an automated scan. A critical finding is reported to you straight away, not saved for the report.

  4. Report and walk through

    You receive the findings report, and we walk your technical team through it, so that each fix is understood before anyone starts on it.

  5. Retest

    Once your team has made the fixes, we test each finding again and update the report, so you can show which issues are closed and which remain open.

Proof

Credentials and partners

Marco Villarruel, Founder & CEO

  • CASE
  • C|CSE

FAQ

Frequently asked questions

What is the difference between a penetration test and a red team operation?

A penetration test tries to find as many weaknesses as possible in a defined scope, such as one application or one network, within two to six weeks. A red team operation has a single goal, such as reaching a particular system, and uses whatever route an attacker would, over four to eight weeks. It tests whether your people and processes notice and respond, not only whether the technology has gaps. Most companies start with penetration testing.

Is the test manual or an automated scan?

Manual. We use tools where they save time, but the findings come from a tester working through your systems the way an attacker would. An automated scan finds known issues in known software; it does not find a flaw in your own business logic or a chain of small weaknesses that together give an attacker control.

Will the test disrupt our systems?

Testing is planned to avoid disruption. We agree the testing window, the systems to treat with care and a contact on your side before we start, and we stop and call if anything behaves unexpectedly. Tests that could affect availability, such as some internal network techniques, are run only with your agreement and at a time you choose.

What does the report contain?

Every finding with its severity, the evidence that shows it is real, the systems it affects and how to fix it, plus a summary your leadership can read without the technical detail. After the retest, the report is updated to show which findings are closed.

Do you fix the issues you find?

The test itself ends with the report and the retest; your team makes the fixes. If you want our help with them, our hardening work for cloud, applications, servers and networks covers it. That is scoped and priced separately, so the people judging whether a fix worked are not marking their own work.

How often should we test?

At least once a year, and again after a significant change, such as a new application, a cloud migration or a merger. Many companies also test before an audit or when a large customer asks for evidence of independent testing.

Related

Threat Detection & SIEM Implementation

SIEM implementation on Microsoft Sentinel, Splunk, Elastic Security or Wazuh, with log sources, detection rules and runbooks handed to your team.

Security Governance

We design your information security program on ISO/IEC 27001 and NIST CSF, with policies, risk and metrics reporting, and a process for assessing suppliers.

The engagement

Duration
2 to 6 weeks; red team operations 4 to 8 weeks
Pricing
Fixed fee

Penetration tests, identity and Active Directory testing and purple team exercises are fixed price. Red team operations are fixed price or time and materials, depending on the project.

  • OWASP
  • MITRE ATT&CK

Next step

Tell us what you want tested

Name the applications, networks or cloud accounts, and any deadline. We reply within two business days.