10 Reasons Why Security Problems Persist at Microsoft

Even though Microsoft would love it when all their security problems disappear, they simply won't. Face it, Microsoft's operating systems are the most common, and hence, the main target. Hackers are more sophisticated than ever; everyday new holes are found in Microsoft products!

Strange thing is, Microsoft is usually aware at least 9 out of 10 holes/vulnerabilities reported, or has that just become a common excuse? Granted, the software giant has had its hands full with signing deals with companies to boost their usage in Europe and Asia, but isn't there something they can do about their flaws?

In recent years, Microsoft has done a slightly better job of addressing security issues. Unfortunately, its efforts haven't been good enough. Security problems still persist in Microsoft products and the chances of them being eliminated in the near future are slim. Here's 10 keypoints why the chances are slim:

  1. Microsoft is a major target
  2. Windows is an easy target
  3. The competition isn't big enough
  4. The company ignored it for too long
  5. Legacy issues
  6. Where's the focus?
  7. Microsoft is usually a step behind
  8. Users can't be trusted
  9. Hackers are more sophisticated than ever
  10. Few consequences

Only 10 reasons?!

View Article



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • When individual departments procure cloud service for their own use, they usually don't consider the hazardous organization-wide implications. Read this paper to learn best practices for setting up an internal, IT-based cloud brokerage function that service the entire organization. Find out how this approach enables you to retain top-down visibility and control of network security and manage the impact of cloud traffic on your WAN.

  • Following an IT incident through to resolution is more than just acknowledging an alert and restarting a server. The recent State of On-Call Report found that it takes most companies an average of 10-30 minutes to resolve an incident with an average of 5 people involved. Imagine how much money and time companies are spending to deal with incident resolution. But what if you had a tool that offered solutions baked in? Or a tool that sent alerts to the right person or team every time? These are the kind of …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date