Industry recognitions we have earned
Before we begin testing, BreachLock™ along with your company will determine the full scope that will be tested. Clear and open discussion with the customer is integral at this step. All communication is facilitated via our SaaS portal which enforces our methodical approach and promotes collaboration between teams. At this stage, we determine the companies’ infrastructure such as domains, servers, and other devices with IP addresses. We then determine if any should be excluded and why. Once we have a list of all of the devices to be tested we can then define the testing duration.
We begin to attack vulnerabilities and known weak spots with your web application. We perform this step with the utmost care in order to protect both the web app and your data. We repeat the penetration process using both manual processes and automated tools. We use many methods such as those prescribed in OWASP methodology. Utilizing our SaaS, we are able to scan your systems in order to find the vulnerabilities that are putting your data at risk. The results of this phase are recorded in PDF and online reports that are made available to you within our SaaS portal.
The BreachLock™ team collects and compiles all of the obtained information and provides the customer with an exhaustive report. We also include comprehensive recommendations to aid business leaders as well as the IT team in order to make logical decisions regarding web application security. We provide a list of each vulnerability, including how we tested and how we recommend resolving the risk. At this stage, we provide specific technical details using which the IT team can act quickly. Our online ticketing system can be used to ask any questions to BreachLock™ security researchers.
After both the business leaders and the IT team are able to read the report and act during the remediation process, we will retest to determine the effectiveness of findings resolution. We will rerun our penetration test on the web application. As a result of the retest, you can download an updated report from within our SaaS portal. This report will either show a clean build or a patched vs not patched status for each finding. If all vulnerabilities are solved we will also issue you a security certificate valid for 12 months.
Requesting a penetration test on your latest release is as simple as clicking a button. Our security researchers swing into action and replicate hacker-like manual penetration testing activity on your cloud infrastructure and applications. You get online as well as PDF reports with screenshots of hacked areas.
Run a Dynamic App Security Tests any time you deploy a release on your staging environment. The scan covers both authenticated and non authenticated parts of the application and produces detailed reports with vulnerabilities and suggestions on fixes.
Run automated scans on your cloud instances to ensure that the operating systems don't leak sensitive information or give way to hackers. Each finding is validated to ensure that you see no false positives despite the automated nature of these scans.
Demonstrate your compliance by introducing multiple checkpoints for security validation before you deploy changes in production. Each finding can be retested after fixes have been deployed. This ensures that you fix application security gaps continuously and prevent any misconfiguration of underlying platforms.
If you are working in the cyber security industry, you will be familiar with terms like application penetration testing, network penetration testing, etc. However, the growth of the cloud computing industry in the last 4-5 Years has introduced a new name to the penetration testing list – cloud penetration testing.
If you are using a Google service which is powered by virtual machines, it becomes your responsibility to ensure that the operating system and the applications are continuously updated and the patches are applied at the earliest.Google recommends that an organization conducts penetration testing for evaluating the security of its cloud infrastructure.
Security testing for User-Operated Services is authorized by AWS, which is created and configured by the user. Pen tests involving Vendor Operated Services, which are owned and offered by the third-party vendor, are prohibited. EC2 and S3 bucket is an AWS service which is usually pen tested.