Risks assessed during a pentest generally focus on attacks perpetrated from outside the information system. Indeed, a classic approach consists of first testing the risks of external attacks (black box pentest), and then the risks of attacks from a customer or partner access (grey box pentest).
Security is one of the main concerns of SaaS application publishers. Security is essential for users to trust the solution and to ensure that data is protected.
Authentication security, data compartmentalisation, data encryption, but also user journey security, service continuity and third-party integrations… The security issues of SaaS applications are multiple. A pentest allows you to assess the robustness of a SaaS platform in order to test and strengthen its security level. Here is a list of subjects that deserve special attention during a pentest.
Mobile applications are part of the elements to secure as they process personal data, access sensitive information, and in some cases enable remote control of devices. Widely used for IoT devices, they are also at the core of the business model of many FinTech, HealthTech and innovative companies from various industries.
Mobile application security encompasses different aspects: the security of the mobile applications themselves (iOS or Android version), the security of the APIs and the security of the servers. Back-end security (APIs and servers) is usually more critical than front-end security (iOS / Android apps), but this depends on the technical and functional context of the application itself.
CREST, OSCP, CEH… Should you require certifications from your pentest providers? To select a pentest provider, security certifications are obviously useful although they cannot be the only way to assess the value of a service and the skill level of pentesters. There are other aspects that should be considered too. Another related topic is the recognition of the pentest value and the certificates that you may be able to show to your customers.
‘Bug bounty signs the end of pentests’ ‘Bug bounty, the death of the traditional penetration test’… Do you remember these article headlines? Today we see that this is not the case and that both approaches continue to exist.
Both services address the same initial need: to test a company’s web applications and infrastructure with realistic attacks. What are the differences between the two approaches? How do you choose between a bug bounty and a penetration test?
We present you nine main criteria to consider.
From a cybersecurity point of view, the dark web is like a huge marketplace where sensitive data (personal data, bank details, email addresses, credentials, etc.) are found alongside kits for carrying out cyber-attacks. Indeed, 15 billion credentials are currently in circulation [1], and it is reportedly possible to buy malware for between $50 and $5000 [2].
Why does business data end up on the dark web? And how to identify possible data leaks? Before we get to the heart of the matter, let’s clarify a few things about the concepts of deep web, dark web and dark net.
Regularly carrying out penetration tests on e-commerce websites ensures a good level of security. This is necessary to ensure the proper functioning of the site as well as the company’s brand image with its customers. But the security challenges are so numerous that it is sometimes necessary to establish priorities.
The network infrastructure is at the core of business operations in most industries. It can be considered the nerve centre of the entire IT organisation because it centralises data, simplifies data exchange and facilitates communication between employees.
It is therefore an essential tool for the smooth running of organisations, which requires constant attention in terms of security in order to protect yourself against increasingly numerous and sophisticated external and internal attacks.
Most web applications manipulate personal and/or business data, in other words, sensitive data. Passwords, email addresses, credit card numbers, health data and others are at the centre of the battle between two opposing sides. On one side, companies, whether small, medium or large, seeking to defend themselves against intrusions into their information systems, and on the other, increasingly experienced attackers, attracted by the lure of gain and stimulated by the many breaches too often ignored by their future victims.
Do you know this half-joke, ‘there is no cloud, it’s just someone else’s computer’? Cloud computing is often seen as THE solution, so it is often overlooked that it is only a tool, with its advantages and disadvantages.
Web and mobile applications are at the core of most companies’ activities. Whether you’ve already deployed them or that they are still under development, some misconceptions about their security are still present, even though it is a crucial topic to conduct your business in good conditions.
Here are the 9 preconceived ideas that we most often encountered.
During a security audit, 3 approaches are possible. They reflect different levels of information and access given to pentesters. The choice of the approach for a penetration testing depends on your objectives: how deep do you want the tests to be? And would you like to test the external or internal threat?
WordPress, Joomla, Drupal, Shopify and many more, offer real possibilities for creating sites that are both ergonomic and efficient. However, a negative image is still associated with CMS websites: they would be insecure and easy targets for malicious hackers.
What are the risks of cyberattacks on these sites? What specific elements of CMS are to be monitored?
If you are in charge of a CMS platform, this article will help you to identify the main risks and will provide you with points of vigilance to reinforce the level of security.