What a penetration test is
A penetration test is a time-boxed exercise in which security testers try to break into your application, API, or cloud account the way an attacker would, with your written permission and within a scope you agree on. Unlike an automated scan, people chain small weaknesses together and check whether each one can really be exploited. You get a report of what they found, how serious each finding is, and how to fix it.
A pentest shows how things stood while the testers were working. It isn't monitoring, and it doesn't keep you secure in the months between tests.
Where Jutsu fits around a pentest
Jutsu doesn't run penetration tests. It works on either side of one: it clears the findings that are cheap to find before you pay for testers' time, and it keeps watching after they leave.
- Before the test: daily checks on AWS, Google Cloud, Azure, GitHub, and your deploy platforms find public storage, remote-access ports open to the internet, missing multi-factor sign-in, and the other misconfigurations testers report first. Cloud security posture assessment lists what they cover.
- Your website and API: Application Monitoring checks a website for certificate expiry, missing security headers, exposed files, and outdated libraries. API Monitoring runs scheduled assessments against the OWASP API Security Top 10, and only on APIs you have verified you own.
- During the test: a pentest is also a chance to see whether your monitoring notices. Jutsu shows which of the testers' actions raised an alert on the systems you have connected, and which didn't.
- Between tests: Red Team runs MITRE ATT&CK-mapped attack scenarios against scoped, authorized targets and measures what your detections caught. It tests your detections, not your application.
- After the test: confirm cloud fixes with Check again, and keep the monitoring and response records that support your SOC 2 readiness.
When a startup needs one
A pentest costs money and your team's time, so it pays to know what is asking for one. These are the usual triggers:
- A customer's security review or questionnaire asks for a recent pentest report, or a summary of one.
- A SOC 2 audit is coming. SOC 2 doesn't make a pentest mandatory, but an auditor or a customer may expect one, and the SOC 2 cost guide shows what it adds to the bill.
- You handle card payments: PCI DSS requires penetration testing at least once every 12 months and after significant changes.
- A big launch, or a major change to how your app handles sign-in, payments, or customer data.
What a startup pentest covers
Scope is the most important decision in a pentest. For a SaaS startup it usually includes some of these:
- Web application: sign-in and sessions, access control between users and between customer accounts, injection, and the other risks in the OWASP Top 10.
- API: authentication, whether one user can read or change another user's data, rate limits, and the risks in the OWASP API Security Top 10.
- Cloud: how your AWS, Google Cloud, or Azure account is configured, who can do what in it, and what can be reached from the internet.
- Sometimes mobile apps, internal networks, or phishing tests, when a customer or auditor asks for them.
How an engagement runs
The steps are much the same whichever firm you hire. How long the testing takes is set by the scope: one web app takes less time than an app, its API, and its cloud account together.
- Scope: which apps, APIs, environments, and user roles are in and out, and whether testing runs against staging or against production with test accounts.
- Permission: written authorization and rules of engagement, with who to call if something breaks, what is off-limits, and when testing happens.
- Testing: the testers work through the scope by hand, with tools to help.
- Report: an executive summary, then each finding with its severity, the evidence, how to reproduce it, and how to fix it. Severities are usually critical, high, medium, low, and informational, often scored with CVSS.
- Fix and retest: you fix the findings, and the testers confirm the fixes. Ask whether a retest is in the price.
- Something to share: ask for a summary or attestation letter you can send customers instead of the full report.
Questions to ask a pentest firm
Pentests are usually quoted per engagement, and the price follows the scope. Before you sign, ask:
- Who does the testing, and what qualifications do they hold (OSCP and CREST are common ones)?
- How much of the work is manual testing, and how much is an automated scan?
- Is a retest included, and for how long after the report?
- Can we see a sample report?
- Will we get a summary or letter we can share with customers?
- How do you avoid disrupting production?
Where Jutsu stops
Jutsu doesn't run penetration tests, write pentest reports, or issue attestation letters, and its automated checks don't replace a tester's judgment. When a customer asks for a pentest report, it has to come from a pentest firm.
