Why Hackers are Having a Field Day

Monday, June 20, 2011

Gurudatt Shenoy

29fb4966bdfcfff5545ae464c771071b

The past few weeks or couple of months have seen a shock and awe campaign being launched by a series of hacker organizations such as Anonymous hackers and LulzSec.

And the pattern was started earlier by WikiLeaks. And seems like so long as Assange is a captive this will go on... No, this is not a conspiracy theory, but it seems like that.

The most serious of recent events is the breach of RSA's SecureID. Whew. If the guardians of security cannot protect their own, who else can?

As these hackers are merrily going about defacing websites and downloading personal information of online users, the cybercops seems to be absent from the scene.

They are busy sewing up the carpet or shoving things inside it after something nasty has happened. And in most cases failing in their efforts miserably as is observed with Sony servers getting hacked over and over again.

This prompted me to put a thought on what is this business about and I could see two things. One a Wikileaks connection and another  weak security.

Of course so called security experts are trying to blame weak code, weak systems, the Chinese and others among many things to take attention away from their own failings.

So, now what can be done about this. How to demolish the efforts of hackers.

Let us start with defacement. If you have a weak administrator password defacement is like having free beer. And if your host is some cheap run of the mill hosting service provider with little or no backend security, then you are fair game for even rookie hackers.

So, the first thing any serious organization has to do to prevent defacement of their websites is to go for a hosting provider that is serious about security.

And test them before you use them. There are a lot of online tools that do just that....You are not required to hire an expensive white hat.

Next, use strong password to control your administrator account. Use an automated password generator that generates a really long and complex password. 

If you have databases powering your websites make sure the database access passwords are also complex. Something that cannot be easily guessed.

If you have an online service, do not present an opportunity for users to define simple passwords or similar passwords. Every password has to be unique if not complex and should have a combination of numbers, special characters and alphabets in upper and lower case. If this is a stumbling block, offer alternative password less authentication solutions.

Encrypt your code on your server. Though there is no way to encrypt all your code, make it difficult for hackers to get to your code and algorithms.

Encrypt your user data before storing on your server. Use a proprietary algorithm that is not commonly available. Make sure the algorithm used to encrypt your data is unique and not available to someone else. Use unique seed keys before encrypting the data. Make sure only the owner / user can decrypt the data. Thus even if the data is downloaded hackers will not be able to decrypt it. 

Strengthen your own in-house security at all critical facilities. Protect your corporate email accounts, intranet, have employees sign water tight NDAs etc. Use in-house monitoring (continuous audio/video) to make sure if a breach occurs you know who it is. 

If organizations do all of this, then even the most expert hacker can be thwarted from doing what they do all the time..

Implementing these does not cost a whale load of money. It only requires foresight and determination to keep hackers from stealing your data, defacing your websites and making fun of your organization. 

Possibly Related Articles:
4371
Network->General
Information Security
Encryption Web Application Security hackers SecurID Password Management Lulzsec
Post Rating I Like this!
Default-avatar
Natalie Geoth Interesting article. However, I have a few comments and suggestions:

- The idea of "demolishing" anyone or anything is purely negative and accomplishes nothing; such an approach will only serve to demolish yourself and those things you care about with negativity and destruction. Instead, I suggest using an important change of mindset to focus on the positive (which may be your intention) and achievable: be humble yet strong in your approach, and replace that phrase with "protect your network". When you suggest "demolish" to someone (in life or IT), they get defensive and may well attack simply out of fear, and this will not help you in your cause.

- Long and strong passwords are an excellent idea. I would suggest that your readers also change their passwords regularly. At this point, a complex password needs to be at least 16 chars long to offset RT's and GPU's. And for users to remember those passwords, suggest schemas to help them, otherwise they cannot and will not create and store them securely in their brain, but will use unsecure methods to help them, and this would greatly reduce the organization security.

- For the proprietary algorithm, I would stick with a public algorithm, since the code review that is done publicly is a highly critical element of security. A proprietary algorithm will be much more vulnerable to attack because the formula is likely not very sound. Even RSA's formulas are very, very good; they just their zippers open enough for some clever nasties to get them. Shame on RSA... They should've known better.

- I read "water tight" as "over-tightening" your NDA. This will drive your employees to fear you because such an NDA is essentially a threat, and people do not work well when threatened. Instead, it will stifle the collaboration that's necessary to create great products and positive feelings about working, which is necessary for sustained high productivity. Tightening the locks will not stop people from doing malicious things; making better locks and incentivizing people to work hard with you will enable you to reap huge rewards, while having a standard, well-worded NDA will give you the teeth you need for those wanting to cause you harm.

- Using in-house audio and video will also stifle creativity and productivity because your employees will be afraid to do much of anything. Being consumed by fear is a negative motivator and serves to foster resentment and distrust. Instead, properly control the IT systems through well-established means. None of the cases you cited are known to have involved an insider, and they likely didn't need one, given what we've read about them. Besides, malicious insiders can usually do what they want despite A/V monitoring.
1308609010
29fb4966bdfcfff5545ae464c771071b
Gurudatt Shenoy I agree...completely. I have always been working on developing security that does not infringe on privacy.

For example, my company has recently launched a password manager called myCloudkey.

This product does not store any personal information or track users.

It encrypts all their passwords using a key that only they (not even our employees) have access to.

Would appreciate your feedback on this product. You can check it out at mycloudkey.com
1312092648
The views expressed in this post are the opinions of the Infosec Island member that posted this content. Infosec Island is not responsible for the content or messaging of this post.

Unauthorized reproduction of this article (in part or in whole) is prohibited without the express written permission of Infosec Island and the Infosec Island member that posted this content--this includes using our RSS feed for any purpose other than personal use.