Security by Design Principles - Revision history

Sytzevk: Sytzevk moved page Secure Coding Principles to Security by Design Principles: misnomer; this is about design, not about coding

2016-08-03T18:35:54Z

Sytzevk moved page Secure Coding Principles to Security by Design Principles: misnomer; this is about design, not about coding

2015-03-05T21:34:08Z

‎Fail securely: fixed minor grammatical error

2009-03-24T20:27:50Z

‎Security Principles

2009-03-24T20:27:41Z

‎Security Architecture

2009-03-24T20:27:30Z

‎Asset Classification

2009-03-01T22:07:00Z

2009-03-01T16:58:30Z

‎Security Architecture

2009-03-01T16:52:24Z

‎About attackers

2009-03-01T16:52:04Z

‎About attackers

2009-03-01T16:51:32Z

‎Asset Classification

@@ Line 106: / Line 106: @@
+  }
-If either <code>codeWhichMayFail()</code> or <code>isUserInRole</code> fails or throws and exception, the user is an admin by default. This is obviously a security risk.
+If either <code>codeWhichMayFail()</code> or <code>isUserInRole</code> fails or throws an exception, the user is an admin by default. This is obviously a security risk.
 ===''[[Don’t trust services]]''===

@@ Line 61: / Line 61: @@
 Security architecture starts on the day the business requirements are modeled, and never finishes until the last copy of your application is decommissioned. Security is a life-long process, not a one shot accident.
-==Security Principles ==
+==Security principles ==
 These security principles have been taken from the previous edition of the OWASP Development Guide and normalized with the security principles outlined in Howard and LeBlanc’s excellent ''Writing Secure Code''.

@@ Line 39: / Line 39: @@
 The following principles are all related to these three pillars. Indeed, when considering how to construct a control, considering each pillar in turn will assist in producing a robust security control.
-==Security Architecture ==
+==Security architecture ==
 Applications without security architecture are as bridges constructed without finite element analysis and wind tunnel testing. Sure, they look like bridges, but they will fall down at the first flutter of a butterfly’s wings. The need for application security in the form of security architecture is every bit as great as in building or bridge construction.

@@ Line 8: / Line 8: @@
 In the last year or so, there has been a significant push to standardize terminology and taxonomy. This version of the Development Guide has normalized its principles with those from major industry texts, while dropping a principle or two present in the first edition of the Development Guide. This is to prevent confusion and to increase compliance with a core set of principles. The principles that have been removed are adequately covered by controls within the text.
-==Asset Classification ==
+==Asset classification ==
 Selection of controls is only possible after classifying the data to be protected. For example, controls applicable to low value systems such as blogs and forums are different to the level and number of controls suitable for accounting, high value banking, and electronic trading systems.

@@ Line 108: / Line 108: @@
 If either <code>codeWhichMayFail()</code> or <code>isUserInRole</code> fails or throws and exception, the user is an admin by default. This is obviously a security risk.
-===''[[Don't trust services]]''===
+===''[[Don’t trust services]]''===
 Many organizations utilize the processing capabilities of third party partners, who more than likely have differing security policies and posture than you. It is unlikely that you can influence or control any external third party, whether they are home users or major suppliers or partners.

← Older revision	Revision as of 18:35, 3 August 2016
(No difference)

@@ Line 54: / Line 54: @@
 Andrew van der Stock calls the above process “Thinking Evil™”, and recommends putting yourself in the shoes of the attacker and thinking through all the possible ways you can abuse each and every feature, by considering the three core pillars and using the STRIDE model in turn.
 By following this guide, and using the STRIDE / DREAD threat risk modeling discussed here and in Howard and LeBlanc’s book, you will be well on your way to formally adopting a security architecture for your applications.
@@ Line 60: / Line 59: @@
 The best system architecture designs and detailed design documents contain security discussion in each and every feature, how the risks are going to be mitigated, and what was actually done during coding.
-Security architecture starts on the day the business requirements are modeled, and never finish until the last copy of your application is decommissioned. Security is a life-long process, not a one shot accident.
+Security architecture starts on the day the business requirements are modeled, and never finishes until the last copy of your application is decommissioned. Security is a life-long process, not a one shot accident.
 ==Security Principles ==

@@ Line 18: / Line 18: @@
 * Disgruntled staff or developers
-* “Drive by” attacks, such as side effects or direct consequences of a virus, worm or Trojan attack
+* “Drive by” attacks, such as side effects or direct consequences of a virus, worm, or Trojan attack
 * Motivated criminal attackers, such as organized crime

@@ Line 24: / Line 24: @@
 * Criminal attackers without motive against your organization, such as defacers
-* [[Script kiddies]]
+* Script kiddies
-[[Category:FIXME|this link doesn't go to anything, we either need to remove the link or add the content this is to link to]]
+[[Category:FIXME|this link doesn't go to anything, we either need to remove the link or add the content this is to link to. I removed the brackets from Script kiddies]]
 Notice there is no entry for the term “hacker.” This is due to the emotive and incorrect use of the word “hacker” by the media. However, it is far too late to reclaim the incorrect use of the word “hacker” and try to return the word to its correct roots. The Development Guide consistently uses the word “attacker” when denoting something or someone who is actively attempting to exploit a particular feature.

@@ Line 10: / Line 10: @@
 ==Asset Classification ==
-Selection of controls is only possible after classifying the data to be protected. For example, controls applicable to low value systems such as blogs and forums are different to the level and number of controls suitable for accounting, high value banking and electronic trading systems.
+Selection of controls is only possible after classifying the data to be protected. For example, controls applicable to low value systems such as blogs and forums are different to the level and number of controls suitable for accounting, high value banking, and electronic trading systems.
 ==About attackers ==