Contact Us Today 01642 716680

cybersecurity

Mobile App Penetration Testing Methodology

Mobile App Penetration Testing Methodology

Mobile Application Penetration Testing often has a different flow to web application or network testing. This is because not only do you get an application but you also get the software itself. This runs on a device you control and allows for a much wider attack surface. It also allows DE compilation of code and hooking of calls all in service of attacking the application. As such, mobile app pentesting requires an entirely different skill set, knowledge base and methodology. Most mobile application penetration tests rely on the OWASP-MASVS (Mobile Application Security Verification Standard). Senior application developers and hackers are responsible for developing this to ensure that applications meet minimum security requirements. The content in this blog comes from the OWASP-MSTG  which is one of the most complete methodologies available. 

Are Wireless Networks Secure?

Wireless networks are generally a weaker alternative to a hardwire connections. Why is this? Well, if the wireless network’s traffic is open, then anyone within range can gain access which means it’s vulnerable to a ‘sniffing attack’. Modern wireless networks get around this by using encryption that requires a secret key.  How are wireless networks … Read more

What is OSINT?

OSINT or Open-source Intelligence is a process of data collection using sources that are open to the public. This can be a wide range of origins – anything from large blogs to specific images and the metadata contained within. Everything posted online discloses some information about the poster and this is what OSINT is looking … Read more

What is Web Application Security Testing?

Web application penetration testing describes the process of simulating an unobtrusive attack against a web application. It allows companies to understand vulnerabilities that are easy to miss during the development process. These vulnerabilities can have wide-reaching consequences to the application as well as the data stored within its database.