Penetration testing
Penetration testing for businesses in Indonesia. We attack your apps, networks and cloud the way a real intruder would, then give you proof of what can be broken and a clear plan to fix it.
Example
One weak point is rarely the problem. The chain is.
This example shows how three small weaknesses join up into a path from the internet to customer data, and how fixing them closes the path.
- Internet
- Public website
- Internal API
- Customer database
- 1FindingForgotten admin page
- 2FindingLogin sessions never expire
- 3FindingAccount has far more access than it needs
Illustrative example. Not client data.
What is penetration testing?
A penetration test, often called a pentest, is a controlled attack on your own systems. You give us permission. We then try to break in using the same methods a real attacker would use.
A scanner can list known weaknesses. A penetration test goes further. A person chains small weaknesses together to show what an attacker could actually reach, such as customer data, payment systems or admin access.
The result is not a long list of theory. It is evidence of what is possible today, ranked by how much it could hurt your business, with a fix for each finding.
When you need a penetration test
- You are about to launch a new website, app or API.
- A customer, partner or regulator has asked for proof of security testing.
- You handle personal data and need to show you protect it, as Indonesia's Personal Data Protection Law (UU PDP) expects.
- Your systems have changed a lot since they were last tested.
- You have never tested them, and you do not know where you stand.
What we test
We agree the scope with you before any testing starts. A test can cover one system or several.
- 01
Web applications
Customer portals, dashboards, online shops and internal web tools.
- 02
Mobile apps
Apps for phones and tablets, and the servers they talk to.
- 03
APIs
The interfaces that connect your apps, partners and services.
- 04
Networks
Internet-facing systems and the internal network behind them.
- 05
Cloud
The accounts, permissions and settings on your cloud platform.
- 06
AI applications
Chatbots, assistants and AI agents, tested for prompt injection and data leaks.
How a penetration test works
Every test follows the same clear steps, so you always know what is happening.
- 1
Scope
We agree what will be tested, when, and what is off limits. You approve it in writing.
- 2
Map
We study the target the way an attacker would, to find every way in.
- 3
Attack
We try to break in by hand, safely, and prove each weakness is real.
- 4
Report
You get every finding in plain language, ranked by risk, with a fix for each one.
- 5
Retest
After you fix the findings, we test again to confirm the gaps are closed.
What you get
- 01
A summary for leaders
One page that explains the risk in business terms, without jargon.
- 02
A technical report
Each finding with evidence, steps to reproduce it and how to fix it.
- 03
A walkthrough
We take your team through the findings and answer their questions.
- 04
A retest
We check your fixes and update the report to show what is closed.
Questions
Questions and answers
What is the difference between a vulnerability assessment and a penetration test?
A vulnerability assessment, or VA, is a mostly automated check for known weaknesses. A penetration test is done by a person who tries to exploit weaknesses and chain them together. The assessment tells you what might be wrong. The test shows you what an attacker can actually do. The two are often combined and called VAPT.
Will the test disrupt our systems?
We plan the test to avoid disruption. We agree the timing and the limits with you first, and we do not run attacks that are designed to take systems offline unless you ask for that. If we find something urgent, we tell you straight away.
How long does a penetration test take?
It depends on the size and number of systems in scope. We give you a timeline when we agree the scope, before any work starts.
How much does a penetration test cost?
It depends on how many systems are in scope, how large they are and how deep the test goes. We start with a short conversation, then write a scope for you to approve. You get the price and the timeline with that scope, before any work starts.
What is the difference between black box, grey box and white box testing?
The difference is how much we know before we start. In a black box test we know nothing, like an attacker from outside. In a grey box test we get limited access, such as a normal user account. In a white box test we can also see the design and the source code. We help you choose when we agree the scope.
How often should we test?
Test before a major launch and after big changes. Many organisations also test on a regular schedule, because both their systems and the attack methods keep changing.
Do you test AI applications?
Yes. We test chatbots, assistants and AI agents for problems such as prompt injection, data leaks and actions the AI should not be able to take. See our AI security page for more.
What do you need from us to start?
A short conversation about what you want tested and why. From that we write a scope for you to approve. For some tests we also need test accounts or access, which we agree with you in advance.
Related services
- Red teamingA simulated attack on your whole organisation that tests whether you can detect and stop it.Learn more →
- Security hardeningWe review and strengthen your servers, cloud, accounts and network so attacks fail.Learn more →
- Security monitoringWe watch your systems for signs of an attack, investigate them and act on steps agreed with you.Learn more →
Contact
Find the gaps first.
Tell us what you want tested. We will reply with a clear scope and next steps.
- Tell us what you need.
- We reply with a clear scope and next steps.
- Nothing starts until you approve it.