Introduction/Overview
Ransomware is growing exponentially, and small companies are no longer immune. Trustvio (real name kept private for security reasons) is an innovative startup that was trying to get their start with their first customers when they were attacked with a $2 million ransomware.
Challenge
SaaS companies will always be a large target for hackers, because of the numerous attack vectors. But Trustvio certainly didn’t expect to be a target
before they onboarded their first customer. Not only did they suer a ransomware attack that they couldn’t possibly aord as a startup, but their first prospects now worried about the integrity of the company. After reporting the attack to the FBI and putting numerous security measures in place, Trustvio searched for a penetration testing company that could produce fast results to give their prospects assurance that they had remediated any weaknesses in their environment.
Solution
Trustvio searched for a fast and aordable partner they could trust, and finally found Red Sentry. Red Sentry provided a full penetration test for their external, internal, and web app environments, and found 37 vulnerabilities. These findings were remediated and Red Sentry provided a letter of attestation that Trustvio could provide to their clients.
Because time was so sensitive to this startup, Red Sentry scheduled the test in 2 business days and had the final report delivered to the company 5 business days later. Other quotes they received required over 3 weeks to schedule and cost over 30% more.
Benefits
Trustvio was able to regain their prospects’ trust and close their first contracts.
High Severity Findings
· MongoDB Backup Exposed
· Insecure Direct Object Reference (IDOR)
· Default Login Credentials
· SQL Injection
Result
Although they will always have a healthy fear of ransomware, the team at Trustvio can move forward more confidently now that they have Red Sentry behind them and a strong security program in place.
Small SaaS Startup hit with $2M ransomware before they even onboard their first client.
SaaS Startup
We strive to bring the best pentest solution, for the cheapest price. And did we mention that we are fast?
We have been making offensive cybersecurity YouTube videos and would love to share our knowledge with you!
Watch YouTubeBelow are just some of the reasons why you should choose Red Sentry.
We make the process smooth. We have no lead times (for those ASAP pentests).
Your PM will communicate with your team throughout the pentest process.
There are no hidden fees or overage fees. The price you see, is what you get.
We offer a retest once you patch up any vulnerabilities.
We make pentesting affordable by cutting out any fluff hourage.
We report all criticals and highs to your team immediately during testing.
Save time, avoid false positives, truly operationalize security, and manage costs.
Check out our pentesting options below.
Once access to the mobile application is granted, all of the models/API endpoints are enumerated, if applicable, the source code is analyzed to look for misconfigurations and sensitive data exposed, the technology stack used is analyzed as well to look for potential CVEs, and the permissions schema is tested to look for broken access controls and privilege escalation possibilities. Overall, the test is conducted following the OWASP Top 10 Mobile methodology.
After scoping, the assessment team tries to access every page of the application and look for the different requests made. From that list, a set of possible attacks is made and then executed to prove impact. A usual requirement here is to look for vulnerabilities that allow a basic user to access either to an admin’s or to another user’s data.
A cloud engagement will look for different misconfigurations inside a Cloud environment that can turn a malicious insider task much easier. The assessment team will look for issues related to the authentication mechanism being used and the virtual assets inside the infrastructure, like database instances, containers, storage buckets and running applications. We will need access to the cloud environment with read only or security audit access to conduct testing. After we gain access to the Cloud, we run a couple of tools to look for both technical and user-generated misconfigurations.
After scoping, an asset discovery is performed to collect all of the active host + port combinations. Once done, we start looking for potential exploits either by searching CVEs associated with the technology stack behind the service running on a certain port, or by performing a set of standard attacks.
Additionally, we look for breached credentials which are still valid on different platforms.
We use different techniques to map the
inside network and then go through a discovery process where we look for privilege
escalation, targets for brute-force attacks, control over traffic data and common
vulnerabilities which could give us access to sensitive information that a regular
user shouldn’t have access to. Depending on the approach chosen, those
vulnerabilities could then be exploited as well.