External pentesting
Assesses what is accessible from the internet. We study its exposure and validate findings within the agreed conditions. It’s used to review the company’s entry points.
- 01IP addresses
- 02Domains
- 03Published services
- 04Exposure
Let’s talkPenetration testing of websites, networks, systems and wifi, with a report, remediation plan and retest.
from €3,000 depending on scope
A penetration test checks whether a vulnerability can really be exploited, within an authorised environment and scope. It’s ethical hacking: the same techniques as an attacker, with permission and rules.
At islaNet we carry out pentesting for businesses in Mallorca that need to assess specific applications, networks or systems. We define the assets, conditions and deliverables before starting.
We give you evidence to understand the risk, prioritise fixes and check that they work. A pentest starts at €3,000, excluding VAT, depending on the scope.
From €3,000
A fixed price before starting, based on the scope.
Retest included
For critical and high findings, within the following three months.
OWASP (WSTG)
The testing guide we follow for web applications.
Signed authorisation
With rules of engagement and agreed time windows.
Before putting a system into production, after a major change, when a client or a standard asks for it, or as a regular review. The engagement turns questions like these into defined tests and assets.
Can a user access information they should not see?
Are there exposed services that would allow someone into the infrastructure?
Does network segmentation prevent access to internal systems?
Have the vulnerabilities already found been fixed properly?
Four types of test, depending on what you want to assess. They can be combined in a single engagement.
Assesses what is accessible from the internet. We study its exposure and validate findings within the agreed conditions. It’s used to review the company’s entry points.
Starts from authorised access to the internal environment to see how far a compromised account or device could get. First we specify the starting point and which actions are permitted.
Reviews login, permissions, sessions and access to information. With several profiles, we check what each user can do and what they shouldn’t be able to. The price depends on the functions and profiles to be tested.
Assesses the networks, access points and their relationship with the company’s systems: for example, whether the guest network is really separated from the corporate one. On-site tests are planned with the premises.
The approach indicates what information and what access we start with.
| Approach | Starting point | What it’s for |
|---|---|---|
| Black box | Little information about the authorised assets. | See what an outsider would find, with no prior knowledge. |
| Grey box | Partial access or documentation, such as accounts for some profiles. | Test specific functions and permissions. |
| White box | Technical documentation and broad access within the scope. | An in-depth review, with knowledge of the architecture and how it works. |
It is chosen according to the goal. The scope also depends on the assets, functions, exclusions and testing time.
Four phases. If anything requires extending the scope during testing, we discuss it before continuing.
Step 1
Which systems are tested and what the limits are. We set owners, working windows, emergency contacts and when testing stops.
Step 2
We review the assets and gather the information that guides the tests. Automated tools detect indications; we decide which ones need validating.
Step 3
We test each weakness only as far as needed to demonstrate it and relate it to the systems and data affected. The report separates what has been demonstrated from what is possible.
Step 4
We deliver the documentation and go through the findings with the owners to clarify priorities. For web applications we follow the OWASP Web Security Testing Guide (WSTG).
Two reports, a plan and a meeting to turn the conclusions into tasks.
for the decision-makers. What was assessed, which significant risks there are and what should be done first, with the limitations of the work.
for the people doing the fixing. Each finding with the affected asset, the test conditions, the evidence, the impact and how to fix it.
the actions in order, with their dependencies: development, IT or an external supplier.
we go through the report with you and with the technicians who will need to act.
The retest reviews the findings once the fixes have been applied and documents whether the problem is resolved, persists or needs further action.
We include the retest of critical and high findings if you request it within three months of the report. If the application or infrastructure has changed a lot, what’s needed is a new assessment.
Before starting we sign the authorisation and the rules of engagement, which cover these six points.
Systems, applications, networks or addresses included.
What is out of scope and which actions are not permitted.
Dates and execution windows.
Contact people and how testing is stopped.
How they are handled, delivered and retained, with sensitive data protected.
Coordination with external suppliers and authorisations for their platforms.
Tests are adapted to each company’s systems and actual activity. They are carried out by Jose Moreno, engineer and CEO of islaNet, who also presents the results.
In a hotel, for example, its own website, the property’s network and another provider’s booking platform may each need their own scope and coordination, and tests are scheduled so as not to cause disruption in high season.
The proposal gives you the scope, timeline, deliverables and a fixed price before starting.
The number and type of applications, networks or systems, and the functions and profiles to be tested.
The information available (black, grey or white box), the level of validation and whether there are on-site tests or working windows.
The reports, the presentation of results and the retest.
They can go into the same assessment, each with its own goal and deliverable.
Reviews controls, configurations, processes and documentation. That’s our cybersecurity audit.
Checks, with authorised tests, whether a weakness can really be exploited.
If you need someone to maintain and review the measures every month, that’s managed cybersecurity.
“For 7 years they’ve handled all the maintenance of our network and workstations. Good professionals and very available.”
Translated from Spanish
Angel Martin
“I have no words to describe everything they’ve done for us.”
Translated from Spanish
Jesús Saa
Mallorcandy
“Very professional. We’ve worked together for many years and there are many more to come!”
Translated from Spanish
Marina Frau
Frau legal
“Thank you for always sorting out our incidents!”
Translated from Catalan
Maria Immaculada Simonet Mateu
“Very happy with IslaNet’s service. They recovered 100% of a broken hard drive for me. Great professionals!”
Translated from Catalan
Enric Gelabert Bautista
“They’re true professionals and specialists in telecommunications and IT services. Dealing with them is direct and personal, and they’re very effective. A top-notch Mallorcan company.”
Translated from Spanish
Raúl Luzón
From €3,000, excluding VAT. The final price depends on the assets, the functions and profiles to be tested, the approach and the depth.
For a web application or an external perimeter, one to two weeks of testing, and the report a week later. The schedule separates preparation, execution, analysis and presentation, and the retest has its own date.
It can, which is why we agree the permitted techniques, the execution windows and when to stop. If appropriate, we work on a test environment and document how it differs from the live one.
Yes, most tests on accessible applications and services. Internal network or wifi tests may need specific access or a physical presence.
At least once a year and after major changes: new features, integrations or the fixing of serious findings.
No: the report says how to fix them. The changes can be made by your team, the application provider or islaNet, and are quoted separately.
No. The result applies to the scope, time and conditions of the assessment, and is read together with the documented exclusions and limitations.
We start with a call.
Tell us which application, network or system you want to assess and what you are worried about. With that we define the scope and prepare the penetration test proposal.
Or call us: +34 871 030 201