Friday, October 30, 2009
How Hackers Find Your Weak Spots
http://www.computerworld.com/s/article/343900/How_Hackers_Find_Your_Weak_Spots?taxonomyId=82
Thursday, October 29, 2009
For U Blackberry Lovers
Wednesday, October 28, 2009
Internet phone systems become the fraudster's tool
This process of breaking into phone company systems is 20 years old and was know as phreaking, but now that phone systems are integrated with the internet it is giving scammers more opportunities to hack. It is now now as VoIP (voice over internet protocol) which is a term used to describe a family of transmission technologies for delivery of voice communications over IP networks such as the internet.
The way the hackers got into these VoIP systems is they just guessed thousands of times what the system's password was. Unlike gmail that will block a user if it makes too many guesses, VoIP systems are not set up this way. If they VoIP has a weak password then it doesn't take long for a computer to figure it out. Once these hackers have access they can launch their attack on bank customers. The problem is that it is hard to track these hackers because they use distant VoIPs that are unrelated to themselves.
Scams like these have been a reoccuring theme this year. It is easy to see how these attacks could be prevented. At the level of the VoIP's, stronger passwords, smarter configurations to prevent password guessing attacks, and increased security could easily prevent hacking from cybercriminals. On the side of the victim I have one word: common sense. Who would give their personal information to an automated message? Never give your personal information out, and if you are worried that there is a problem with your billing information call your bank.
Tuesday, October 27, 2009
16 Year Old Hacks NASA haha
Jonathon James became the first juvenile to be sent to prison for hacking at the age of 16 years old. Through our knowledge from this class, James claimed to be gray hat hacker. In an anonymous PBS interview James was quoted saying, “I was just looking around, playing around. What was fun for me was a challenge to see what I could pull off."
James’s actions were directed towards prestigious and important institutions. One institution affected was ironically the Department of Defense. He installed a backdoor into a Defense Threat Reduction Agency server. The DTRA is an agency of the Department of Defense charged with reducing the threat to the U.S. and its allies from nuclear, biological, chemical, conventional and special weapons. The backdoor he created enabled him to view sensitive emails and capture employee usernames and passwords.
Another important institution the 16 year old compromised was NASA! NASA claimed that the boy stole over 1.7 million dollars worth of software. The Department of Justice claimed that the software stolen directly controlled the Space Station’s physical environment, including control of the temperature and humidity within the living space. NASA had to shut down its computer systems which cost them 41,000 dollars. How could a 16 year old boy hack into what millions of people base their safety upon? His response, "The code itself was crappy . . . certainly not worth $1.7 million like they claimed."
With all of the intrusions compiled against James, he would have served at least ten years as an adult. Due to his age, he was banned from computer use and was forced to serve a six-month sentence under house arrest with probation. The funniest part is that he then served six months in prison for violating his parole. James now claims that he learned his lesson and is in the process of starting a computer security company. Regardless, Jonathan James will always be known as the sixteen year old who hacked NASA!
If someone would have asked me what NASA should do to prevent hackers before I read this article, I would’ve said that their security is way beyond my technical knowledge. Although I’m sure the 16 year old was extremely knowledgeable, this should not have been possible. NASA obviously needs to add more firewalls and more up to date virus software. Most importantly, NASA and DTRA should conduct vulnerability tests. Vulnerability tests will highlight flaws and limitations on their systems and can show areas that may need improvement.
Wednesday, October 21, 2009
Reflections of Insecurity
Friday, October 16, 2009
Notre Dame Federal Credit Union
Tuesday, October 13, 2009
Hotmail Security Breach
On October 6th, Murad Ahmed and Elizabeth Judge reported in an article in the Times Online that Hotmail, the world's most popular e-mail provider, was the victim of an internet phishing scam. As we have previously discussed in this class, phishing is the process by which individuals are tricked into disclosing private information, including but not limited to names, passwords, and financial details, by malicious people pretending to represent a legitimate business operation.
Microsoft, owner of the e-mail service, admitted that 10,000 hotmail.com, msn.com, and live.com accounts were illegally accessed, the details of which were shared by the hacker on a website that caters to technology experts. This information has since been removed and a Microsoft spokesperson noted, "We are working diligently to help customers regain control of their accounts.
According to Tom Warren, the Neowin.net reporter who broke the case, the majority of the Hotmail accounts that were breached had European addresses and could possibly be British. This is notable as Hotmail is about one and a half times larger than its closest competitor in Britain and, with this, becomes "the latest in a long line of big organisations, from the UK Government to major banks, who have been faced with internet security breaches recently."
If this security breach is, as claimed, the result of a phishing scam, then most of the blame falls on the account holders who surrendered their private information. In this case, the compromised users should establish new accounts or change their current settings to ensure security. However, if it turns out to be the result of an error in Hotmail's operation or a direct attack on its system, then it seems that Microsoft must be held accountable to its users in some way.
Source: http://business.timesonline.co.uk/tol/business/industry_sectors/technology/article6861965.ece
Monday, October 12, 2009
Smart Grids: The Future of Electricity
In order to make the smart power grid secure, the utility companies must keep their computer systems secure so hackers cannot exploit the vulnerabilities presented with the smart grid. Utility companies must first keep the data of how much electricity is flowing back and forth between the utility company and the end users confidential. The companies must also have safeguards in place to prevent hackers from modifying the flow of electricity which will protect the integrity of the smart grid. Finally, the utility companies must make sure the smart grid works so electricity is available to the end users.
In contrast to the utility companies’ security goals, attackers are going to try and exploit the smart grid. They will attempt to disclose confidential information to gain access to the data on electricity flow, alter the flow of electricity between end users and utility companies, and deny end users and utility companies’ access to electricity.
IOActive, an application and smart grid services provider, made comments on the vulnerabilities of the smart grids with Richard Adhikari of technewsworld.com “research has been conducted throughout the industry and has concluded that the power grid is susceptible to common security vulnerabilities such as protocol tampering, buffer overflows, persistent and non-persistent rootkits and code propagation”. Potential attacks will focus on these vulnerabilities.
The inherent risk with the smart grid technology lays in the dependency on the internet and having to rely on Internet Protocol. The risk of having a major breach in the security of smart grids can result in situations ranging from problems, such as people getting away with paying their power bill and can be as serious as terrorists gaining complete control of the system and causing mass blackouts across the United States.
In order to prevent this from happening utility companies must use centralized log management systems, which can track when and where cyber security threats exists and how to respond to those threats. There should also be third-party assessments made on the smart grids to ensure the security of grids are being audited.
Sources:
Smart Meters and Security: Locking Up the Grid by Richard Adhikari
Radiation Overdoses
Thursday, October 8, 2009
Networking Slides
Monday, October 5, 2009
Credit Card Use
Even more scary is the fact that, of the five times I used a credit card, three times I swiped the card myself. This means that a criminal could have easily used "white plastic" (a plain card with nothing but a magnetic strip) if my card was ever "skimmed." The use of white plastic also occurred in the TJX case we studied. The cashier would never even notice that the card was fraudulent, which should be easy to spot, because the criminal would be able to swipe the card himself or herself.
Once again, it appears that the biggest risk in information security lies with human error. The technology is all there, and it works. However, it is when people are either too careless or too lazy to verify a persons identity that puts people at risk for fraudulent charges. The only reassuring news is that it is the business itself or the bank that will ultimately pay should the fraudulent charges occur.
Sunday, October 4, 2009
Computerized Time Clocks
The owners of this technology expect that the computerized time clocks will protect the integrity and availability of the information that is stored on them. They expect that the identity of the employee, the number of hours that each employee works, and the task that the employee performs is authentic, and they also expect that the employees are consistently able to interact with the system. These expectations are part of the overall expectation that the time clock will be consistent, easy to use, and accurate. Also, as an employee interacting with the system, I would expect that my information would be kept confidential.
An attacker could want to exploit this system in several ways. The most frequent attacker of a system like this would be an employee attempting to make more money than he or she earned for the tasks that he or she performed or the number of hours worked. Other attackers could include competitors who want to shut down operations by either violating the integrity of the information, shutting the system down so that employees could not clock in, or disclosing personal information of employees like bank account numbers, assuming that the time clock software connects to the bank for direct deposit.
The biggest risk inherent to this system is that it is not monitored as thoroughly as traditional time clocks and is more vulnerable to employee dishonesty or tampering as a result. Like I said, at my job at home it is the employee’s responsibility to enter into the computer which task he or she performs that shift. Breaching the integrity of this system is as easy as telling the computer that I worked a higher paying job than I actually did every so often. Also for this organization, the employee identification number is only four numeric digits long, so it would be very easy for other employees or outside attackers to access my personal information.
As a manager who would use this technology I would mitigate my risks by putting several safeguards in place. To reduce my risk I would either make my employees’ identification numbers longer, or I would require them to enter two forms of identification to clock in. I would also make sure that my employee’s information was protected to insure that their bank account numbers were not vulnerable to theft. Finally, I would check the information stored by the computerized time clock at regular intervals to protect myself against expensive employee dishonesty.
Friday, October 2, 2009
Facebook's Newest Challenge
The Captcha used by Facebook is supposed to be top of the line, leading to speculation that humans may have done it manually. In fact, there is the possibility that people were paid to enter the information necessary for each account. Tasks like this could even be outsourced for a very small amount of money. Based on my own experience with registering for Facebook, I find either of these scenarios likely. However, if someone has created a program which can bypass human involvement with Captchas, then this would pose a significant security threat for many different websites, and it would be important that Captchas be improved.
The URL which these profiles are trying to spread has already been blacklisted by most web browsers and disabled from being shared on Facebook. This URL is the same as one that was early being spread through compromised accounts of actual people. Furthermore, Facebook has already publicized that users should be wary of clicking on strange links. Using common sense, most people should know better than to click on a link sent to them by someone who they do not know, especially since most of the messages in which these links are contained are obviously not legitimate. However, as we have learned, many people using the Internet lack this type of common sense. Facebook may need to improve their user verification system. I had heard of the possibility that a cell phone number could be used. After signing up, Facebook would send a text containing a code to the new user, and that code would be used to activate the account. Repeat cell phone numbers could not be used. However, this would eliminate people who do not have cell phones or texting from using Facebook, even if they are legitimate. Since this idea may not be realistic, Facebook will need to continue to monitor accounts, and users need to be aware of these schemes.
Source: http://www.computerworld.com/s/article/9138780/Facebook_Captchas_broken_?taxonomyId=17