Trustwave Unveils New Offerings to Maximize Value of Microsoft Security Investments. Learn More

Trustwave Unveils New Offerings to Maximize Value of Microsoft Security Investments. Learn More

Services
Capture
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

twi-managed-portal-color
Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

twi-briefcase-color-svg
Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

tw-laptop-data
Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

twi-database-color-svg
Database Security

Prevent unauthorized access and exceed compliance requirements.

twi-email-color-svg
Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

tw-officer
Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

tw-network
Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Microsoft Exchange Server Attacks
Stay protected against emerging threats
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
SpiderLabs Blog

What Do Bug Bounties Cover?

Over the past few days in the UK we have been bombarded with arguments and debates over the use of Facebook and other social networking sites due to the riots that we witnessed all over the country. However, in the background, with not too many people hearing much about it - a man from York, the place where I have spent most of my childhood, has been arrested and let out on bail for trying to hack into Facebook.

From the news stories that I heard the most contested point regarding this has been to do with what information he has gained and why Facebook didn't find out about this sooner. The real questions we should be asking ourselves though is why didn't he receive the bug bounty and why has he been arrested with possible extradition to the USA?

Okay so what he did went well beyond what the bug bounty will cover, he maliciously gained access to servers that he should not have had access to but the question, again, is what constitutes as too far when it comes to finding bugs in and vulnerabilities in the vendors applications and software.

The first point that I want to make is that for a bug bounty to be honoured you have to first abide by a responsible disclosure policy when it comes to telling the vendor about the problem that you have found. When I say this, you will probably have to wait until the bug has been fixed as companies won't pay out for bugs that are still available to attackers (I would like to be proven wrong, leave a comment if you have seen this happen before).

Secondly, when you find a bug that potentially will allow you access to servers and machines that you're not supposed to be able to use - you should probably stop there and not go any further. You officially are already breaking laws trying to find bugs in websites i.e using single quotes to find SQL errors or queries - by going further you are moving further away from what is right and what is wrong.

Why are you doing this anyway? Did you just log onto Facebook one morning and decide that you were going to try and find a problem with the website? Web application testing is a form of penetration testing that can take a while to sort out legally. You need to sign NDAs and make sure everything is insured incase anything goes wrong etc. Imagine attempting to inject a query into the Facebook or Twitter application and it dropping the DB by accident? You would not be praised, especially if the last backup they made was over a few days old!

To be on the safe side, if you want to know what the bug bounty covers you for or what you are actually allowed to do - you should ask. It is always best to be up front as what you are doing isn't wrong, otherwise they wouldn't pay you for your research. As long as you are cooperative and don't try and hide what your doing, you SHOULD be alright.

 

Latest SpiderLabs Blogs

Search & Spoof: Abuse of Windows Search to Redirect to Malware

Trustwave SpiderLabs has detected a sophisticated malware campaign that leverages the Windows search functionality embedded in HTML code to deploy malware. We found the threat actors utilizing a...

Read More

The Sentinel’s Watch: Building a Security Reporting Framework

Imagine being on shift as the guard of a fortress. Your job is to identify threats as they approach the perimeter. The more methods you have for detecting those threats, the better your chances of...

Read More

Fake Advanced IP Scanner Installer Delivers Dangerous CobaltStrike Backdoor

During a recent client investigation, Trustwave SpiderLabs found a malicious version of the Advanced IP Scanner installer, which contained a backdoored DLL module. Our client had been searching for...

Read More