Call us on 0845 077 8883

Ancar B Technologies – IT Support Yorkshire
reports »

Network Support in Leeds, Bradford and throughout West Yorkshire



Posts Tagged ‘reports’

Commonly used passwords exposed and recommendations

May 4th, 2010

Users with weak passwords are the primary security vulnerability within many organizations IT infrastructure. Users generally forget passwords fairly regularly unless the password is something easy to remember or pertinent to them. This method for generating passwords makes them susceptible to dictionary attacks.

A recent report by the DB Security Company Imperva based on 32 million passwords exposed from  the rockyou.com security breach has highlighted patterns and the most popular passwords used. The full report is available here.

The Top Ten Common Passwords

The Top Ten common insecure passwords are:

  1. 123456
  2. 12345
  3. 123456789
  4. Password
  5. iloveyou
  6. princess
  7. rockyou
  8. 1234567
  9. 12345678
  10. abc123

Key findings:

  • About 30% of users chose passwords whose length is equal or below six characters.
  • Moreover, almost 60% of users chose their passwords from a limited set of alpha-numeric characters.
  • Nearly 50% of users used names, slang words, dictionary words or trivial passwords (consecutive digits,  adjacent keyboard keys, and so on). The most common password among Rockyou.com account owners is “123456”.

The effect to businesses

Even though Microsoft are trying to enforce password policies in the design of their Active Directory infrastructures, many IT Administrators are disabling these features at the request of management. This is causing major vulnerability.

In our market place, the Microsoft Small Business Server is key to many SME network deployments, and features such as Remote Web Workplace, Outlook Web Access and VPN access are enabled for many users.

The flaw to this is that in an SME environment the number of users is small, and as such usernames are generally easy to guess as many companies use just First Names as the username. It’s much easier for a hacker to attempt a brute force attack on First name combinations rather than the more complex First name Last Name permutations.

For example, the username of “chris” who has a password of “123456″ or “Password” is going to be very easy to break. If Chris happens to be at Director level, there is going to be no end of information that can be accessed by the hacker.

Our Recommendations for Usernames

So our recommendation in a business domain is that usernames are based on a pattern that is not directly related to First Names, but either has a prefix or is based on First name and Last Name to infinitely increase the username possibilities. If you’re signing up to a web site that shows a “Screen” or “Nick” name, ensure this is different to your username.

Our Recommendations for Passwords

Using passwords based around your name, family, or words found in a dictionary are not secure as these are the basis for simple dictionary attacks. Many websites now offer a scale of complexity when signing up provide a guide to users about their passwords. It should contain a mix of four different types of characters – upper case letters, lower case letters, numbers, and special characters such as !@#$%^&*,;” If there is only one letter or special character, it should not be either the first or last character in the password.

So to sum up, in a business and web environment it is important that both your usernames and passwords are designed to increase complexity to reduce the effectiveness of a Brute Force attack, and never use one of the passwords listed above.

The problem with Virtualisation

April 13th, 2010

Many companies have been moving to Virtualisation over the last two years since the hype has hit the market, but many of the deployments have been classed as failures by management within the business. This is caused by many businesses taking the decision to virtualise core services, without the correct planning and expectations. In the end, they have major performance issues and degredation

It is true that physical servers are under utilised. According to reports, the majority of servers are used approximately 15% of the time that it is powered on. So how or why are these deployments failing? Well, usually bad resource planning and undefined project definable deliverables and I will try to outline some of the major failure points in this post.

1. Resource Planning

When planning a Virtualisation deployment needs time. In a multi server environment you need to monitor resource usage of your existing physical servers, or have a solid understanding of their needs when planning the architecture and specification within your Virtual Infrastructure. You need to know, which services and physical services can blend well to ensure that a physical node isn’t overloaded and a performance decrease is witnessed.

Key items to monitor include:

  • Processor idle time
  • Page File use
  • Free Memory
  • Disk Queue Length
  • Bandwidth

2. Additional Network Complexity

Consolidation of your physical environment into a Enterprise/Private Cloud has many business and IT advantages, which include reducing the network complexity. Ironically without the correct training, many IT Administrators and Support Teams are failing to be able to support the the solutions correctly due to a poor understanding of the architecture.

3. Hidden underlying costs

Tied with number one, poor planning of an installation can leave companies needing to add additional servers and complexity into their Virtual networks that weren’t initially planned. With the addition of more servers usually comes the deployment of a Storage Network which adds another costly layer to the deployment.

4. Unrealistic Expectations

In a Virtualised environment, you are sharing server resources. It will be inevitable, that there will become a queue on a specific resource demand at some point and a performance drop will be seen over ths queue length.

You cannot expect to receive the performance of a single server from within a Virtual environment without the correct investment.

5. Not utilizing High Availability

One of the best features that Virtualisation and Cloud computing offers is the ability the fail over ability. The Virtual Machines are not dependent upon hardware, so can be simply configured to move from server to server in the event of failure.

Now as this can be a “Server Consolidation Exercise“, many companies do not use this feature and this can leave them in peril. In our current networks, if one server fails, one service is unavailable. However, if a virtualised node fails, all the servers hosted on their fail, potentially taking down the entire network.

Businesses suffering extended IT outages are statistically more likely to suffer massive financial losses and potentially fold.

Is it all bad?

Definately not, No! Ancar B is an advocate for Virtualisation, and with the correct planning and budget all SME users can take advantage of the benefits whether it be in house or hosted.

Had a bad experience?

If you’re working on a current virtual network and you’re suffering with resource overuse or performance degredation, I suggest you take a look at your performance monitors and see where improvements are needed or bottlenecks occur.

If you’re in a Windows environment, check Microsoft’s Measuring Performance on Hyper-V to help shed some light.

Hopefully, this post will allow you to avoid any issues in depolying a Virtual Network, or just a little insight into the traps that are out there.