---
title: "Penetration Testing"
url: "https://grc.plus/lv/service/penetration-testing/"
type: "Service"
updated: "2026-11-06"
publisher: "GRC+"
---

Security testing

# Penetration Testing

We attack your applications, networks and cloud environments the way a real attacker would, within a scope and rules of engagement you agree first. You get each finding with its evidence, its risk and a fix.

![OffSec Certified Expert (OSCE)](https://grc.plus/wp-content/themes/grcplus/assets/img/credentials/osce.webp)

[Download the Service Sheet (PDF)](https://grc.plus/service/penetration-testing/pdf/?v=fb315401)

[Book a 30-Minute Call](https://meetings-eu1.hubspot.com/ahmet-ucar)

Scope Your Test

**500+** Regulations Laws and standards

**40** Countries Europe, Gulf, Asia and North America

**25+** Years In regulated sectors

**9** Industries From banking to healthcare

Why it matters

## Your customers and auditors want proof your systems resist attack

The problem

### A scanner is not a test

Automated tools find known issues. They miss business logic flaws and chains of small weaknesses, and fill reports with false positives.

The solution

### A test that thinks like an attacker

We combine tools with manual testing, confirm what can really be exploited and stop before it causes harm.

The outcome

### A short list of real problems

You know what an attacker could do, what to fix first and how, and a retest shows auditors the fix works.

Is a test required?

## When a regulation, standard or customer asks for a test

We scope the test to what your requirement asks for, so the report serves that audit as well.

[Latvia DORA (LV-DORA) · Art. 24-25 Risk-based testing programme with penetration tests; critical systems tested at least yearly. Read the Requirement](https://grc.plus/regulation/digital-operational-resilience-act-dora/latvia/)

[Industry scheme PCI DSS · Req. 11.4 Internal and external penetration tests at least every 12 months and after significant changes. Read the Requirement](https://grc.plus/regulation/payment-card-industry-data-security-standard-pci-dss/)

[Industry scheme Swift CSP · Control 7.3A Swift users penetration-test their Swift infrastructure regularly and after significant changes. Read the Requirement](https://grc.plus/regulation/swift-customer-security-program-swift-csp/)

[International standard expected ISO 27001 · Annex A 8.8, 8.29 Technical vulnerabilities identified and assessed; security tested in development and acceptance. Read the Requirement](https://grc.plus/regulation/iso-27001-information-security-cybersecurity-and-privacy-protection/)

Customers

### A customer's security review

A recent independent test report, with a retest of the fixes, is a common ask in a vendor review.

Scope and effort

## What do you want tested?

Pick what is in scope. We confirm it, with dates and a fixed fee, in your proposal.

Targets

Web application or API

Mobile app

Desktop app

External network

Internal network

Cloud account

Wi-Fi

User roles in the application

Not sure yet

1

2 to 3

4 or more

Internet-facing addresses

Not sure yet

Up to 16

17 to 64

More than 64

Environment

Not sure yet

Test environment

Production, in agreed windows

Use This in My Proposal Request

## What we test

### Applications

With and without a login, against the OWASP guides.

### Infrastructure

What an attacker reaches from outside, and from inside.

### Cloud and containers

Permissions, exposure and configuration of accounts and Kubernetes.

[Cloud Security Assessment](https://grc.plus/service/cloud-security-assessment/)

### Exposure

What attackers already know, and validated scanning.

How it runs

## From scope to verified fixes

1. 1
  Scoping
  Targets, user roles, test windows and exclusions, with written authorisation and rules of engagement.
2. 2
  Testing
  Automated and manual testing in the agreed windows. A critical finding is reported to your contact the same day.
3. 3
  Report and walkthrough
  Findings with evidence, risk and a fix, a management summary and a session with your team.
4. 4on request
  Retest
  We check your fixes and update the report, so you can show the result to auditors and customers.

### From your side

A named contact who can stop the test, the targets and test accounts and clear limits on what is out of scope.

### Risk kept low

Agreed windows, no destructive techniques and a call straight away if we see instability.

### What a test cannot promise

No test finds every weakness. The report states what we tested, how and in what time.

What you get

## How we differ from a scan

- Manual testing, not an automated scan sold as a test
- Every finding verified by hand before it reaches the report
- A practical fix for each finding, rated for your business
- A retest of your fixes on request
- Results mapped to NIS2, DORA, ISO 27001, PCI DSS and Swift CSP
- Professional indemnity insurance on every engagement

FAQ

## Penetration testing: frequently asked questions

Something else? Ask us in a 30-minute call.

[Book a 30-Minute Call](https://meetings-eu1.hubspot.com/ahmet-ucar)

**How often should we run a penetration test?**

At least once a year and after significant changes, such as a new application or a major release. Some frameworks and contracts set their own frequency.

**Do you test production systems?**

Where you agree. Many tests run on a production-like test environment; tests on production use agreed windows and safe techniques.

**Which standards do you follow?**

Recognised methods, including the OWASP Web Security Testing Guide for web applications and NIST SP 800-115 for technical security testing, with findings rated on a common risk scale.

**Which kind of penetration test do we need?**

Start from what worries you or what your customer or regulator asks for. An internet-facing application points to a web test, a concern about ransomware to an internal network test. We help you choose on the first call.

**Should you test production or a test environment?**

A test environment close to production is usually safer, and lets us try actions we would not try on live data. Some issues only show in production, so we can agree a careful test there too.

**What do you need to test our app?**

A test build for each platform, or access through your app store testing track, plus test accounts. Builds without extra protection let us spend the time on your code rather than on removing it.

**Show 16 More Questions**

**What is a thick client?**

A program installed on a workstation that does part of its work locally and talks to a server, such as a banking back-office tool or a trading terminal.

**What is the difference from a vulnerability assessment?**

A vulnerability assessment finds and validates weaknesses. A penetration test goes further and exploits them, to show what an attacker could actually reach. Many organisations run assessments often and penetration tests less often.

**How often should we run a vulnerability assessment?**

Many organisations run one each quarter and after major changes. Some standards and customers set their own frequency, which we take into account when we plan with you.

**Do we have to follow the CIS Benchmarks?**

No. They are a recognised starting point, and we can use your own standard. Where a setting would break something you rely on, we note it and suggest what to do instead.

**Is OSINT legal?**

We use public sources, respect the law and do not sign in with leaked credentials. Personal data we meet is kept to what the work needs and handled under agreed confidentiality terms.

**Do you need to be on site?**

Yes, for wireless testing someone has to be within range. We agree the locations and times with you, and test each site or a representative sample.

**Could a penetration test disrupt our systems?**

Testing carries some risk, because systems are used in ways they were not built for. We agree test windows and exclusions in advance, avoid destructive techniques and tell you straight away if we see instability.

**What do you need from us for a web application test?**

The address of the application or the API documentation, test accounts for each role, and a contact who can help if something stops working.

**Do you test the app protections too?**

Yes, on request. Root detection, pinning and obfuscation slow an attacker down, so we can test how well they hold. They do not replace fixing the underlying flaws.

**What do you need from us for a desktop application test?**

An installer or a prepared workstation, test accounts for each role, and access to a test backend.

**How do you run an internal test?**

Usually through a small device or a virtual machine on your network, or a VPN connection you provide. It starts from a standard user or visitor position, which you choose with us.

**Is a vulnerability assessment enough for compliance?**

It depends on the requirement. Some ask for scanning, others for penetration testing as well. We tell you which applies to you before you commit.

**Do you need administrator access?**

Read access with enough rights to see the configuration is normally enough, using an account you create for the assessment and remove afterwards.

**How does this relate to a red team test?**

It is often the first phase. Run alone, it gives you a fast view of your exposure at a lower cost than a full exercise.

**Will testing disturb our users?**

We do not jam networks or disconnect users unless you explicitly ask for that test and agree a time for it.

**What does penetration testing cost?**

The fee follows your scope. You receive a written proposal with scope, dates and a fee before any work starts.

## Plan your penetration test

In 30 minutes you learn what is in scope, how we would approach it and what drives the fee. A written proposal follows within two working days. [sales@grc.plus](mailto:sales@grc.plus)  [+31 20 241 66 00](tel:+31202416600)

Related: [Red Teaming](https://grc.plus/service/red-teaming/)[Source Code Review](https://grc.plus/service/source-code-review/)

[Book a 30-Minute Call](https://meetings-eu1.hubspot.com/ahmet-ucar)

Get a Quote
