Cybersecurity

How to choose a penetration testing company in Jamaica

By Syxel Technologies · · 8 min read
Two security testers working at computer screens

A penetration test is a controlled attack on your systems by people you have hired to do it. Done well, it shows which weaknesses an attacker could actually use and what they could reach. Done badly, it is an automated scan with a logo on the front. Both may be sold as a "penetration test", so it pays to know what to look for before you sign. This guide explains how to choose a penetration testing company, whether you are a credit union in Kingston, a hotel on the north coast or a software firm with customers overseas.

Be clear on what you need

Start by separating two services that are often confused. A vulnerability scan uses automated tools to list possible weaknesses, such as missing patches or exposed services. A penetration test goes further: testers try to exploit what they find, chain small problems together and show what an attacker could reach. Scans are useful and cheaper to repeat; a penetration test answers the question "could someone actually get in?"

Then decide what to test. Common options are external network testing of internet-facing systems, internal network testing from inside the office, web application testing of portals and online services, wireless testing of business and guest Wi-Fi, and cloud configuration review. Your reason for testing shapes the choice: a regulator or client contract, a new application going live, a recent incident, or simply wanting to know where you stand. Our penetration testing page describes each type.

What a professional penetration testing company will insist on

Written authorization

Testing systems without permission is an offence, so a reputable firm will not start until someone with the authority to approve it has signed a written authorization. If any systems are hosted by a cloud provider or web host, the firm should confirm that testing is allowed under that provider's terms. Be wary of anyone willing to start on a verbal go-ahead.

A written scope and rules of engagement

The scope lists exactly which IP addresses, domains, applications and sites are included and which are excluded. The rules of engagement cover the testing window, techniques that are off limits (most businesses exclude anything likely to knock systems offline), contacts on both sides, and what happens if the testers find something critical part-way through.

A recognized methodology

Ask which methodology the testers follow. Common references include the OWASP Web Security Testing Guide for web applications, the Penetration Testing Execution Standard (PTES), and NIST SP 800-115, a technical guide to security testing. A firm does not need to follow one rigidly, but it should be able to explain its approach and show that testing is structured and repeatable.

Manual testing, not just a scanner

Automated tools cover ground quickly, but they miss flaws in business logic, weak access controls between user roles and small issues that combine into something serious. Ask how much of the work is manual and who does it.

Judge the report before you hire

The report is what you are paying for, so ask for a redacted sample. A good one has an executive summary in plain English for owners and boards, and a technical section for your IT team or developers. Each finding should include a description, evidence that it is real, a risk rating and specific steps to fix it. Findings should be ranked so you know what to do this week and what can wait. A debrief meeting to walk through the results is a sign the firm expects you to act on them.

Retesting and what happens next

Ask whether retesting of fixed findings is included or quoted separately. A retest confirms the fixes worked and gives you evidence for auditors or clients. Many organizations test at least once a year and again after major changes, such as launching a new application, and use managed security monitoring to keep watch between tests.

Confidentiality and your data

Testers may see customer records, staff details or financial data while they work. Under Jamaica's Data Protection Act, that information still has to be protected, so the contract should cover confidentiality, how evidence is stored, who can access it and when it is deleted after the engagement.

Questions to ask a penetration testing company

  1. What exactly is in scope, and what is excluded?
  2. Which methodology do you follow, and how much testing is manual?
  3. What credentials and experience do the people doing the testing hold?
  4. Can we see a redacted sample report?
  5. How will you contact us if you find something critical during testing?
  6. What techniques will you avoid so our systems stay up?
  7. Is retesting included, and within what period?
  8. How do you store, protect and delete our data and test evidence?

Warning signs

  • A price before anyone has asked what you want tested.
  • No written authorization or scope document.
  • Promises that your systems will be "unhackable" after the test.
  • Reluctance to share a sample report or explain the methodology.
  • A report that is a raw scanner export with no explanation of risk or fixes.

Local or overseas?

Overseas firms can do excellent work, especially for internet-facing systems. A Jamaica-based firm has some practical advantages: the same time zone for urgent calls during testing, the ability to come on site for internal network and wireless tests, and familiarity with local systems, providers and the Data Protection Act. Whoever you choose, the checks above apply.

How Syxel Security approaches penetration testing

We do not test anything without written authorization and an agreed scope, and we confirm third-party hosting permissions first. Our testers combine automated scanning with manual testing. You receive a report with a plain-English executive summary and a technical section, followed by a debrief, and we can retest fixed findings. Our team holds (ISC)² SSCP and ISACA credentials. If you are not ready for a full test, a security gap analysis is a good place to start. See our full range of cybersecurity services.

Frequently asked questions

What is the difference between a vulnerability scan and a penetration test?

A vulnerability scan uses automated tools to list possible weaknesses. A penetration test goes further: testers try to exploit those weaknesses, combine them and show what an attacker could actually reach. Scans are good for regular checks; penetration tests answer whether someone could really get in.

How often should we have a penetration test?

Many organizations test once a year and again after major changes, such as launching a new application, moving systems to the cloud or opening a new site. Regulators, insurers or client contracts may set their own requirements.

Will a penetration test disrupt our systems?

A well-run test is planned to avoid disruption. The rules of engagement set the testing window, exclude techniques likely to knock systems offline and name contacts on both sides, so any unexpected effect can be dealt with straight away.

How long does a penetration test take?

It depends on the scope: the number of systems, applications and sites, and whether internal or wireless testing is included. A firm should give you a timeline once the scope is agreed.

Do testers need to visit our office?

External network and web application tests can be done remotely. Internal network and wireless tests usually need someone on site, or a device placed on your network, because they test what can be reached from inside.

Get a quote