Penetration Testing for Organizations
A penetration test examines the organization the way an attacker would: what is reachable from the internet, what can be achieved from one workstation inside the network, and which weaknesses (vulnerabilities) in websites, the cloud and work processes open a way in. At the end you get a report with findings rated by risk and fix recommendations (remediation), and when the same provider also manages the infrastructure, the fixes are carried out and tested again (retest).
Seeing the organization
through an attacker’s eyes
A penetration test starts with written authorization, a defined scope and agreed rules of engagement. The testing itself is coordinated and uses methods that don’t harm the production environment, and it ends with a report that explains what was found, what the risk is and what to fix first.
- Internal network and Active Directory, internet-facing systems (external perimeter), websites and APIs
- Recognized methodologies: OWASP WSTG, PTES and NIST SP 800-115
- Executive summary, findings rated by CVSS and a retest
Interactive illustration
What a penetration test looks like, step by step
Choose a stage to see what we do in it and what you get from it.
What we do
Together we define what is tested and what isn’t, which method is used (black, grey or white box), during which hours and who to coordinate with. The test starts only after written authorization.
What you get
A signed scope and authorization document, a contact person who is available throughout the test, and confirmation that there is a current backup before we start.
Who it’s for
Suppliers to large organizations
That need to present a recent penetration test in a security questionnaire, a tender or a contract renewal with a customer or a cyber insurer.
Regulated organizations
That hold personal data under the Privacy Protection Law and the Data Security Regulations, or work to ISO 27001, and want to know whether the controls written in their procedures also hold up in a hands-on test.
Businesses after a significant infrastructure change
A move to the cloud, a new system exposed to the internet, connecting a branch or merging networks. After a change like that it’s worth checking what opened up along the way (attack surface).
Sound familiar?
These are the reasons organizations come for a penetration test, often after they’ve already been asked to present one.
- A large customer or a cyber insurer requires a recent penetration test report, and there isn’t one
- An automated vulnerability scan returned a long list, and it’s unclear which items are actually dangerous
- No idea what an attacker could achieve from one compromised workstation (lateral movement)
- Services exposed to the internet over the years: remote access, a portal, a forgotten admin interface (exposed services)
- The website or system was built by an outside vendor, and nobody has checked its security
- A previous test ended with a thick report, and the findings weren’t fixed because nobody was there to do the fixing (remediation)
Types of tests and what you get at the end
The types of test are chosen based on what is exposed, what is sensitive and what is required by customers or a regulator.
Internal penetration test (internal PT)
What can be achieved from inside the network: Active Directory, permissions, passwords, unpatched servers, network separation (segmentation) and lateral movement.
External test (external PT)
Testing what is exposed to the internet (external perimeter): the firewall, remote access and VPN, mail servers and open services.
Websites, web applications and APIs
Testing against OWASP WSTG and the OWASP Top 10: authentication, permissions between users, injection, business logic and APIs.
Cloud, Microsoft 365 and Google Workspace
Configuration review: conditional access policy, MFA, external file sharing, app permissions and admin accounts.
Wireless networks (Wi-Fi)
The separation between the guest network and the corporate network, the encryption and authentication method, and unauthorized access points (rogue AP).
Social engineering
A phishing simulation and a check of phone verification procedures, coordinated with management. Results are presented at the organization level, not as a list of employees.
Findings report
An executive summary, technical findings with a CVSS risk rating, and a clear fix recommendation (remediation) for each finding.
Remediation and retest
Carrying out the fixes when the infrastructure is our responsibility, or supporting the provider that manages it, and retesting every finding that was fixed.
What we take care of, in detail
Types of tests
- Internal test (internal PT): network, Active Directory, permissions, servers and workstations, from the point of view of a compromised workstation, an employee or a guest on the network
- External test (external PT): exposed addresses and services, VPN, remote access (RDP, RD Gateway), mail servers and management interfaces
- Websites, web applications and APIs, including WordPress, portals and systems developed for the organization
- Cloud configuration review: Microsoft 365, Entra ID, Google Workspace and Azure
- Wi-Fi networks: guest separation, authentication method (WPA2 / WPA3 Enterprise), unauthorized access points (rogue AP)
- Social engineering: phishing simulation, phone impersonation (vishing) and a check of verification procedures
- Vulnerability assessment as a periodic check between penetration tests
How we work and methodology
- Written authorization from the organization, scope definition and agreed rules of engagement before any action
- Black box, grey box or white box: how much information and access the tester gets in advance
- OWASP WSTG and the OWASP Top 10 for websites and web applications, PTES and NIST SP 800-115 for infrastructure
- Non-destructive methods in the production environment, and sensitive tests in a staging environment when there is one
- A coordinated testing window, a contact person in the organization available throughout the test, and a stop condition
- Verifying that there is a working backup that can be restored (restore test) before the test starts
- Secure storage of the findings and of what was collected during the test, and deleting them at the end as agreed
Report, remediation and retest
- Executive summary: what was found, what the business risk is and what to fix first
- Technical findings with a CVSS risk rating, business context and documentation showing that the finding exists (evidence)
- A practical fix recommendation (remediation) for each finding, including a temporary workaround when the full fix is complex
- A wrap-up meeting with management and the IT staff
- Carrying out the fixes in infrastructure we manage, or supporting the provider that manages it
- A retest and an updated report based on what was closed
- Including the findings in the risk register and in the information security work plan
From the first conversation to an organized routine
- 1
Introductory call and defining the goal
What is driving the test: a customer requirement, regulation, a change in the infrastructure or wanting to know where the organization stands.
- 2
Scope, authorization and rules of engagement
Defining the scope, the type of test, time windows and a contact person, and signing written authorization and the rules of engagement.
- 3
Running the test
Coordinated testing with methods that don’t harm the production environment, and updating the contact person during the test as soon as a critical finding comes up.
- 4
Report, remediation and retest
Presenting the findings to management and the IT staff, carrying out the fixes (remediation) and retesting what was closed.
What to know before ordering a penetration test
A penetration test is meant to find weaknesses before they come to light in a real incident, with downtime, exposure of customer data and an inquiry by the Privacy Protection Authority. Tests vary a great deal in depth and in what they leave behind, so it’s worth understanding a few things before defining the scope:
Vulnerability scan vs. penetration test
A vulnerability assessment is an automated check that compares versions and settings against a list of known weaknesses, and returns a long list without context. In a penetration test, the tester verifies which findings can actually be exploited, chains several small weaknesses into one attack path and shows what it allows in practice. Both are needed: frequent scans, and an in-depth test at longer intervals.
Black box, grey box and white box
In a black box test the tester starts with no prior information, like an outside attacker. In grey box they get a regular user or partial information, which is the scenario closest to an employee whose account has been compromised. White box includes access to documentation, settings and sometimes code, and allows broader coverage in the same amount of work time.
Methodology and risk rating
A professional test follows a documented methodology: OWASP WSTG and the OWASP Top 10 for websites and web applications, PTES and NIST SP 800-115 for infrastructure. Every finding is rated by CVSS and by its impact on the business, so management sees what is urgent and the IT staff know what to fix. A report without ratings and without practical recommendations is hard to turn into a work plan.
Authorization, scope and rules of engagement
A penetration test is carried out only with written authorization from whoever is authorized to give it, within a defined scope and under agreed rules of engagement: what is tested, what is out of scope, at what hours and who the contact person is. In production, methods that don’t disrupt service are used, and before work starts we make sure there is a working backup. When a system is hosted by a cloud or hosting provider, its testing policy is also checked in advance.
What happens after the report
The value of a penetration test is measured by what gets fixed after it. When the test is done by the provider that manages the servers, the network and the permissions, the findings turn directly into a remediation plan, are carried out in the infrastructure with change documentation (change management) and are tested again. When testing and fixing are separate, even a good report often ends up in a drawer.
Guide: Internal versus external penetration test: the difference and what fits your organization
Frequently asked questions
About penetration testing in your organization.
Didn’t find an answer? +972-3-3801180
There is no single frequency that fits every organization. It’s common to run a full test at regular intervals, for example once a year, and also after a significant change: a new system exposed to the internet, a move to the cloud or a change in the network structure. The Data Security Regulations require periodic penetration tests for databases at a high security level, and customers and insurers often set requirements of their own. Between tests, periodic vulnerability scanning finds new weaknesses.
Any active testing carries some risk, so the test is built to minimize it: non-destructive methods in production, a coordinated time window, an available contact person in the organization and checking in advance that there is a working backup. Especially sensitive tests are run in a staging environment when there is one, or outside working hours. If something behaves unusually, we stop and update the contact person.
In black box the tester starts with no information, like an outside attacker. In grey box they get a regular user or partial information. Grey box usually gives more value for the work time, because it tests the common scenario of a compromised employee account (account takeover) and doesn’t spend most of the time trying to get in.
A report with an executive summary that explains the risk in business terms, and a technical section in which each finding is rated by CVSS, with documentation showing that it exists and a clear fix recommendation (remediation). After the fixes are made, a retest is carried out and the report is updated. The report can be presented to customers, to the insurer or as part of an audit.
Some customers and standards require a tester who is not the party that manages the infrastructure, and it’s worth checking this in advance. The advantage of a test by the IT provider is that the findings don’t stay in the report: whoever tested knows the infrastructure, fixes it and tests again. When independence is required, the two can be combined: a test by an independent party, and we handle the fixes and the retest.
Yes, at a fitting scope. Even a small office usually has Active Directory or Microsoft 365, remote access and a website, and many attacks look for exactly the common weaknesses in these. A focused test, for example an external test (external PT) together with a Microsoft 365 configuration review, gives a clear picture without a big project.
More you can centralize with us
Information security and cyber for organizations
An outsourced CISO, risk management and compliance, hardening, penetration tests, monitoring and response to cyber incidents (incident response).
Internal Penetration Test (PT)
What an attacker already inside the network can achieve: attack paths in Active Directory, excessive permissions, weak passwords, unpatched servers and lateral movement.
Website, Web Application and API Penetration Testing
Testing websites, portals and APIs against OWASP: authentication, permissions between users (IDOR), injection, business logic, file uploads and exposed configuration.
Want to know what an attacker would find in your organization?
Tell us briefly about your business and what concerns you about your IT. We’ll get back to you to understand what you need and suggest a way of working that fits.
Business hours: Sunday to Thursday, 09:00 to 17:00
Existing client? Open a support ticket