Internet-facing infrastructure
Servers, services and devices the company exposes to the internet: email, remote access, websites and panels. We check whether they can be used to get inside.
CYBERSECURITY · PENETRATION TESTING
At your request we check whether your safeguards can be broken: within an agreed scope and time window, on rules written down before we start. You get evidence, not a list of theoretical threats.
A penetration test goes deeper than an audit. An audit shows what is misconfigured. A test checks whether someone could exploit it and how far they would get.
You run an online shop, a customer portal or a system with customer data that is reachable from the internet.
A client, an insurer or a tender requires a penetration test report.
You are launching a new system, moving to the cloud or changing how remote work is set up.
You want to check that the fixes really close the door to an attacker.
Servers, services and devices the company exposes to the internet: email, remote access, websites and panels. We check whether they can be used to get inside.
Login, sessions, permissions (can a user see someone else's data), injection, configuration. We follow the OWASP Web Security Testing Guide and OWASP ASVS.
What someone who is already inside can do: an employee's infected computer or a guest plugged into the network. Whether one computer is enough to take over the whole network.
A test can start with no knowledge of the system (black box), with an ordinary user account (grey box) or with access to documentation and code (white box). The more we know at the start, the more real problems we find in the same time. For applications we usually recommend grey box.
Written authorisation, a list of targets, a time window, contact people and what is out of scope. If the system runs at an external provider or in the cloud, we check whether its terms require consent or notification.
We follow recognised methodologies: OWASP, PTES and NIST SP 800-115. We verify every finding from automated tools by hand, so the report contains no false alarms. A critical flaw is reported immediately, without waiting for the end of the test.
A summary you can follow without technical knowledge, and a description of each flaw: CVSS severity, steps to reproduce, evidence and remediation advice.
After remediation we test the flaws again and confirm in the report which ones are closed. You can implement the fixes yourself or with us.
We keep the risk to a minimum: we test within an agreed time window, we don't run load tests, and before testing production systems we make sure there is a current backup. Where possible, we test on a test environment.
The law does not set one frequency for everyone. Many industry standards expect a test at least once a year and after every significant change to the system. The actual cycle is best matched to the risk and to your clients' requirements.
A scanner automatically flags possible flaws. A penetration test checks by hand which of them can be exploited, chains them together and shows how far an attacker could get. An exposure scan is even more cautious: it uses public information only.
Yes. In infrastructure and cloud services we implement the fixes, and because we build software every day, we also fix application code — in your own applications and in ones we built for you.
If you have no application of your own and no requirement from a client, an IT security audit is usually the better choice. It will show whether, and which, systems need testing.
Tell us what you want tested. We'll agree the scope on a short call.
WE REPLY WITHIN 24 HOURS
Describe what you want tested: an application, servers or the network. We'll agree the scope and the rules of the test.
JET LARK SP. Z O.O.
3 MAJA 22 / 2C
40-096 KATOWICE, POLAND
Your message has taken off. We'll get back to you within 24 hours — keep an eye on your inbox (and the spam folder, just in case).