Difference between revisions of "Laws of Security"

From MgmtWiki
Jump to: navigation, search
(Full Title and Meme)
Line 3: Line 3:
  
 
==Source==
 
==Source==
The first known publication of the laws is in the book "Writing Security Code" Michael Howard and Dave LeBlanc <ref>Michael Howard and Dave LeBlanc, ''Writing Secure Code, Second Edition (Developer Best Practices) 2nd Edition'' (2013) Microsoft ISBN ISBN 978-0735617223</ref>..
+
The first known publication of the laws is in the book "Writing Security Code" Michael Howard and Dave LeBlanc <ref>Michael Howard and Dave LeBlanc, ''Writing Secure Code, Second Edition (Developer Best Practices) 2nd Edition'' (2003) Microsoft ISBN ISBN 978-0735617223</ref> in 2001.
  
 
[https://technet.microsoft.com/en-us/library/hh278941.aspx Ten Immutable Laws Of Security (Version 2.0)] is a recent version, now rebranded as "Microsoft laws" with no reference to Michael Howard at all. Their are other references to different Microsoft personnel as authors to various versions. The following list is from the anonymous version 2.0.
 
[https://technet.microsoft.com/en-us/library/hh278941.aspx Ten Immutable Laws Of Security (Version 2.0)] is a recent version, now rebranded as "Microsoft laws" with no reference to Michael Howard at all. Their are other references to different Microsoft personnel as authors to various versions. The following list is from the anonymous version 2.0.

Revision as of 11:23, 16 July 2018

Full Title and Meme

Ten Immutable Laws Of Security

Source

The first known publication of the laws is in the book "Writing Security Code" Michael Howard and Dave LeBlanc [1] in 2001.

Ten Immutable Laws Of Security (Version 2.0) is a recent version, now rebranded as "Microsoft laws" with no reference to Michael Howard at all. Their are other references to different Microsoft personnel as authors to various versions. The following list is from the anonymous version 2.0.

  1. If a bad guy can persuade you to run his program on your computer, it's not solely your computer anymore.
  2. If a bad guy can alter the operating system on your computer, it's not your computer anymore.
  3. If a bad guy has unrestricted physical access to your computer, it's not your computer anymore.
  4. If you allow a bad guy to run active content in your website, it's not your website any more.
  5. Weak passwords trump strong security.
  6. A computer is only as secure as the administrator is trustworthy.
  7. Encrypted data is only as secure as its decryption key.
  8. An out-of-date antimalware scanner is only marginally better than no scanner at all.
  9. Absolute anonymity isn't practically achievable, online or offline.
  10. Technology is not a panacea.

References

  1. Michael Howard and Dave LeBlanc, Writing Secure Code, Second Edition (Developer Best Practices) 2nd Edition (2003) Microsoft ISBN ISBN 978-0735617223