SWA Hacking Challenges to the World
Hack our Server Protection Product - FortressTM





Learn More about the Server Challenge: Click Here


Learn more about the Server Challenge Product - FortressTM: Click Here





SWA Products Solve These Problems
Real Life Examples by Industry


Healthcare



RANSOMWARE

What really happened: Hackers logged into the hospital's remote access portal and planted ransomware using a 3rd party login and password. Over 1,400 critical files were compromised and the hospital paid $47,000 in ransom to have their files unlocked.

What could have happened: The FortressTM protected server used where the 3rd party had login privileges would not allow ransomware to affect any files outside those in the 3rd party vendor's directory. No files lost. No ransomware paid.

DATA THEFT

What really happened: A researcher discovered hospital patient records from several hospitals on the dark web, over 655,000 in total. HIPPA fines can range from $100 to $50,000 per record.

What could have happened: Using FortressTM to protect the server, the patient data would not have been taken.

LOSS OF OPERATIONAL ABILITY

What really happened: A major hospital chain was hit so hard by the virus "WannaCry" that they cancelled patient operations and asked patients not to come to the hospital unless it was absolutely essential as they could be turned away.

What could have happened: Using FortressTM on the servers and DrawBridgeTM on the workstations, the hospital would continue operations as the virus infection would not spread. "WannaCry" could be blocked against future attacks.

LOSS OF LIFE

What really happened: Researchers were able to hack the pacemaker in a $100,000 medical dummy made to resemble an actual patient. They were able to speed up the pacemaker and "kill" the dummy. Seven different medical devices were flagged as vulnerable to hacking.

What could have happened: Using a special version of FortressTM, known as KnightWingTM, the medical devices could be hidden behind and protected by KnightWingTM so they could not be found by hackers to attack them.



Education



DATA LOSS

What really happened: A state university database was hacked. Names, social security numbers and school ID's were exposed. The university must spent and extra $1 million/year in cybersecurity costs to protect faculty, staff and student data. Over 1,400 critical files were compromised and the hospital paid $47,000 in ransom to have their files unlocked.

What could have happened: The social security numbers and school ID's were on a server protected by FortressTM and their theft did not occur.

DDOS ATTACK

What really happened: A DDos attack was launched against a university causing the university network to become very slow or inaccessible. The attack was from vending machines, smart light bulbs and other IoT devices on campus.

What could have happened: FortressTM has very high resistance to DDos attacks and continues to function through them. A variation of FortressTM could front the IoT vending machines and stop hackers from attacking them.

DATA LOSS

What really happened: A hacker has stolen 77 million user account details from a popular education platform. Email addresses of K-12 students, faculty, and parents have been exposed.

What could have happened: FortressTM has very high resistance to DDos attacks and continues to function through them. A variation of FortressTM could front the IoT vending machines and stop hackers from attacking them.

LOSS OF OPERATIONAL ABILITY

What really happened: The university network was hacked from China and they had to shut down all servers and recover them.

What could have happened: The servers were protected by FortressTM and were not able to be hacked. So no shutdown, no reputation impact.



Government



DATA THEFT

What really happened: In a single state, hackers were able to infiltrate a Dept of Commerce data system and access around 5.5 million social security numbers. The estimated cost to fix is $3 million.

What could have happened: The social security numbers were protected by being on a server protected by FortressTM and their theft did not occur.
DATA THEFT

What really happened: Personnel records of 4.2 million US government employees were stolen. SF-86 forms were stolen for 21.5 million government employees, contractors and others. Background investigator interviews with friends and relatives of these personnel were also stolen along with 5.6 million fingerprints. US government paid pay $133 million to protect victims with identity theft insurance.

What could have happened: The data was on a server protected by FortressTM, the theft did not occur.

WEBSITE VANDALISM

What really happened: Websites for four US states were hacked and replaced with ISIS messages.

What could have happened: FortressTM includes a web application firewall that will protect against attacks. The server itself will limit the implanting of files and alert on any alterations.

LOSS OF OPERATIONAL ABILITY

What really happened: Two different counties have been shutdown in the US due to ransomware. Services are suspended and it will take weeks or months to have all the computers back in service.

What could have happened: FortressTM is in use for the servers and DrawBridgeTM is in use for the workstations and, if the ransomware is successful, it will be limited to a single user's data rather than spread through the network.



Defense



EMAIL SYSTEM TAKEOVER

What really happened: The unclassified email system of the Joint Chiefs of the US DeparTMent of Defense was taken over. Access was via a phishing attack to get on the network and then attack other computers. The network had to be taken down to stop the attack.

What could have happened: The unclassified email system was running on a FortressTM server and could not be hacked. The users were using DrawBridgeTM protected workstations and, if one was hacked, the attack did not spread throughout the network.

SERVER VULNERABILITIES

What really happened: A researcher found many vulnerabilities in DOD systems due to misconfigured systems.

What could have happened: FortressTM protects the DOD servers and warns if it is misconfigured or changed in anyway that makes it unsecure.

COMPUTER HACKED

What really happened: A pentagon official's computer was compromised when they clicked on a Twitter link. Attacks could then move throughout the network.

What could have happened: What could have happened: The pentagon network was using FortressTM on its servers and DrawBridgeTM on its workstations. 100's of thousands of malware sites were blocked stopping the attack. If the attacker did compromise the single computer, none of the other workstations or servers in the network could be hacked.

WEBSITE VULNERABILITY

What really happened: The Navy/Marine Internet was hacked by Iranians through a security gap in one of the Navy's public facing websites. No data was taken but an estimated $10 million was spent in cleanup.

What could have happened: The websites were on a FortressTM protected server which includes a Web Application Firewall (WAF). The security gap was closed. If somehow the attacker got through, all other servers were protected by FortressTM and workstations by DrawBridgeTM and the attack would have gone nowhere.


Resellers