1. OWASP Cornucopia Ecommerce Website Edition
OWASP Cornucopia - Ecommerce Website Edition: Helps developers identify security requirements from the OWASP Secure Coding Practices - Quick Reference Guide
Some suppliers/vendors are mentioned: OWASP does not endorse or recommend commercial products or services
Colin Watson
Blackfoot UK Limited

2. SAFECode - Practical Security Stories and Security Tasks for Agile Development Environments

3. OWASP Secure Coding Practices – Quick Reference Guide

4. Microsoft Elevation of Privilege (EoP) Card Game

5. Downloads for EoP

6. EoP is excellent, but a few things I wasn't so keen on
Not web application specific enough
A few Microsoft-isms
Less up-to-date
No cross-referencing
Impersonal
(Limited operating system support)
OWASP does not endorse or recommend commercial products or services

7. Resource constraints
No desktop publishing software (Adobe In Design and Illustrator)
No designer
No budget
Not much time
OWASP does not endorse or recommend commercial products or services

8. More web application relevantü
EoP examples
An attacker could squat on the random port or socket that the server normally uses
An attacker can confuse a client because there are too many ways to identify a server
An attacker can make [your authentication system|client|server] unusable or unavailable [without ever authenticating] [but the problem goes away when the attacker stops|and the problem persists after the attacker goes away] (10 cards)
An attacker can provide a pointer across a trust boundary, rather than data which can be validated
Cornucopia examples
Gary can take over a user's session because there is a long or no inactivity timeout, or a long or no overall session time limit, or the same session can be used from more than one device/location
Marce can forge requests because per- session, or per-request for more critical actions, strong random tokens or similar are not being used for actions that change state
Eduardo can access data he does not have permission to, even though he has permission to the form/page/URL/entry point

9. More coverage of web security requirementsü
EoP suits = STRIDE
Spoofing Impersonating something or someone else
Tampering Modifying data or code
Repudiation Claiming to have not performed an action
Information Disclosure Exposing information to someone not authorized to see it
Denial of Service Deny or degrade service to users Elevation of Privilege Gain capabilities without proper authorization
Cornucopia suits
Data validation and encoding Input and output data validation and escaping
Authentication Verification of identity claims and related processes
Session management Maintenance of user state
Authorization User/role permission controls
Cryptography Hashing, digital signatures, encryption and random number generation processes and their usage including key management
Cornucopia (everything else) Including information leakage, data loss, dependencies, abuse of trust, non-repudiation, configuration management, function misuse, denial of service

10. Less colourful and less pictorialü û
EoP playing cards
Cornucopia playing cards

11. Less vendor specific and more webapp/OWASP specificü
EoP examples
An attacker could take advantage of .NET permissions you ask for, but don’t use
An attacker can alter information in a data store because it has weak ACLs or includes a group which is equivalent to everyone (“all LIve ID holders”)
Cornucopia examples
Bob can influence, alter or affect the application so that it no longer complies with legal, regulatory, contractual or other organizational mandates
You have invented a new attack of any type
Read more about application security in OWASP’s free Guides on Requirements, Development, Code Review and Testing, the Cheat Sheet series, and the Open Software Assurance Maturity Model
You have invented a new attack against Authorization
Read more about this topic in OWASP’s Development and Testing Guides

12. ü More information rich EoP Suit name (e.g. Denial of Service)
Attack description
Ranking (card number)
Cornucopia
Suit name (e.g. Authentication)
Attack description
Ranking (card number)
Cross-referencing Security requirements, security verification checks, attack detection points, attack patterns and Agile user stories

13. More individual ü
EoP
An attacker could steal credentials stored on the server and reuse them (for example, a key is stored in a world readable file)
An attacker can manipulate data because there’s no integrity protection for data on the network
An attacker can provide or control state information
An attacker can say “I didn’t do that,” and you’d have no way to prove them wrong
Cornucopia
Shamun can bypass input validation or output validation checks because validation failures are not rejected or sanitized
Kyun can access data because it has been obfuscated rather than using an approved cryptographic function
Keith can perform an action and it is not possible to attribute it to him

14. ü What's in a name? The “names” can represent
External or internal people
Aliases for computer system components
The application itself
Other applications
Services
Operating systems
Infrastructure
Jim can undertake malicious, non-normal, actions without real-time detection and response by the application

15. Print your own Word document Media Business card pre-scored sheets
Other card (and knife/scissors)
Colour printer
Some time
OWASP does not endorse or recommend commercial products or services

16. Identifying requirements with each card played
Suit and value
Attack description
Cross-referencing
Is this a viable attack for the function/system under consideration?
Document the attack
Subsequently use the cross- references to help create security requirements:
User stories
Unit tests
Configurations
etc

17. Example: Third party hosted payment form 1/3
Common e-commerce implementations
Merchant-managed e-commerce implementations
Proprietary/custom developed shopping cart/payment application
Commercial shopping cart/payment application
Shared-management e-commerce implementations
Third-party embedded application programming interfaces (APIs) with Direct Post
An inline frame (or “iFrame”) that allows a payment form hosted by a third party to be embedded within the merchant’s page(s)
Third-party hosted payment page which redirects the consumer to a page on an entirely different domain for payment entry
Wholly outsourced e-commerce implementations

18. Example: Third party hosted payment form 2/3
The template used at the third party could be modified by an attacker

19. Example: Third party hosted payment form 3/3
Content on the page is included from a less trusted source
JavaScript
CSS
Images
Another third party (e.g. metrics, hosted JavaScript library)
First party (i.e. merchant)

20. Deal the deck of cards Outcomes:
Players have the same number of cards each
Randomly select one player to lead the play for the first round e.g. Ferdinand
Erik
Ferdinand 9 A 10 7 2 2 8 4 Q 8 9 J 10 A 4 J K 8 5 7
Imogen
Martin

21. Let play commence – First round
1 0
0 0
Requirements Rounds
1 1
0 0
Requirements Rounds 10 7 8 7 3 J K J A 8
Erik
Ferdinand
Assume every player Except “Imogen” identified a security requirement, thus 1 point each for the others
“Ferdinand” won the round with the King so he gets an additional 1 point, and leads the play for the next round
Schedule of requirements
Imogen
Martin 8 4 Q 9 2 9 5 A 10 2
0 0
0 0
Requirements Rounds
0 0
1 0
Requirements Rounds

22. Second round 1 0 1 0 Requirements Rounds 1 1 2 1 Requirements Rounds
1 0
1 0
Requirements Rounds
1 1
2 1
Requirements Rounds 10 7 7 3 J J A 8
Erik
Ferdinand
Only “Ferdinand” and “Imogen” identified new requirements and they each receive 1 point
“Martin” won the round with the Ace so he gets 1 point for that, and leads the play for the next round
Schedule of requirements
Imogen
Martin 8 4 Q 9 9 5 A 2
0 0
1 0
Requirements Rounds
1 1
1 0
Requirements Rounds

23. Third round 1 0 2 0 Requirements Rounds 2 1 3 1 Requirements Rounds 10
1 0
2 0
Requirements Rounds
2 1
3 1
Requirements Rounds 10 7 7 J A 8
Erik
Ferdinand
Everyone identified new requirements and they each receive 1 point
“Imogen” won the round with the Queen so she gets 1 point for that, and leads the play for the next round
Schedule of requirements
Imogen
Martin 8 Q 9 9 5 2
2 1
1 0
Requirements Rounds
2 1
1 1
Requirements Rounds

24. Fourth round 3 0 2 0 Requirements Rounds 3 1 4 2 Requirements Rounds
3 0
2 0
Requirements Rounds
3 1
4 2
Requirements Rounds 10 7 J A
Erik
Ferdinand
Everyone identified new requirements and they again each receive 1 point
“Ferdinand” won the round with the Jack so he gets 1 point for that, and leads the play for the final round – he also has the most points so far
Schedule of requirements
Schedule of requirements
Imogen
Martin 8 9 5 2
3 1
2 1
Requirements Rounds
3 1
2 1
Requirements Rounds

25. Fifth and final round 3 0 3 0 Requirements Rounds 5 2 4 2
3 0
3 0
Requirements Rounds
5 2
4 2
Requirements Rounds 10 A
Erik
Ferdinand
Everyone except “Erik” identified new requirements and they each receive 1 point
“Imogen” won the round with the 8 (trumps) so she gets 1 point for that
Overall Ferdinand wins the game with a total of 7 points
Schedule of requirements
Schedule of requirements
Imogen
Martin 8 2
4 2
3 1
Requirements Rounds
4 1
3 1
Requirements Rounds

26. Choose your deck of cards
Cornucopia suits
Data validation and encoding Input and output data validation and escaping
Authentication Verification of identity claims and related processes
Session management Maintenance of user state
Authorization User/role permission controls
Cryptography Hashing, digital signatures, encryption and random number generation processes and their usage including key management
Cornucopia (everything else) Everything else including information leakage, data loss, configuration management, denial of service
Full deck

27. Application-specific decks
Cornucopia suits
Data validation and encoding Input and output data validation and escaping
Authentication Verification of identity claims and related processes
Session management Maintenance of user state
Authorization User/role permission controls
Cryptography Hashing, digital signatures, encryption and random number generation processes and their usage including key management
Cornucopia (everything else) Everything else including information leakage, data loss, configuration management, denial of service
Public information website f
Extranet

28. Development-specific decks
Cornucopia suits
Data validation and encoding Input and output data validation and escaping
Authentication Verification of identity claims and related processes
Session management Maintenance of user state
Authorization User/role permission controls
Cryptography Hashing, digital signatures, encryption and random number generation processes and their usage including key management
Cornucopia (everything else) Everything else including information leakage, data loss, configuration management, denial of service
Organisation's coding and configuration standards or
Compliance requirements (e.g. PCIDSS)
Framework X

29. Does Cornucopia matter?

30. Project on the OWASP wiki

31. Project plan Improvements Framework-specific card decks
Enhance text and mappings
Further developer feedback
Issue further releases
Translations
Design and print
Other editions
(Ecommerce website)
Web services
Mobile app
Smart meter

32. Another way to print/obtain the cards
OWASP Corncucopia is free to use
Creative Commons Attribution-ShareAlike 3.0 license
You are free to
Share - copy and redistribute the material in any medium or format
Adapt - remix, transform, and build upon the material
for any purpose, even commercially.
Under the following terms
Attribution
ShareAlike
Travelex
Created print-ready designs
Uploaded these PDF files back to the OWASP wiki
Blackfoot
Create source image files and PDF print- ready designs
Gifted these files back to the project
Printed 100s card decks
Gifted 250 to OWASP
Giving the others away free of charge through their website
OWASP does not endorse or recommend commercial products or services

33. Now with design ?

34. The project OWASP Cornucopia
Mailing list
Download Cornucopia Ecommece Website Edition v1.03
This presentation
???
Colin Watson
colin.watson(at)owasp.org

35. Something else - Help needed for OWASP Code Review Guide
Manual Review - Pros and Cons (
360 Review: Coupling source code review and Testing / Hybrid Reviews (
Code Review Approach ( I am not sure about this subject. It seems to me it would be covered in the above section under Code Review Introduction.
Application Threat Modeling ( Update this section. I am going to take this one.
Understanding Code layout/Design/Architecture (
SDLC Integration ( Update this section
Secure Deployment Configuration (
Metrics and Code Review ( Update this section
Source and sink reviews (
Code Review Coverage ( Update this section
Risk based approach to Code Review ( I am not sure about this subject. It seems to me it would be covered in the above section under Coder Review Introduction.
Code Review and Compliance ( Update this section
Please contact Larry Conklin

36. Something else 2 - Help needed for OWASP Testing Guide
4.6.5 Testing for Insecure Direct Object References (OTG-AUTHZ-005)
4.6.6 Testing for Failure to Restrict access to authorized resource (OTG- AUTHZ-006)
4.6.7 Test privileges of server components (OTG-AUTHZ-007) (e.g. indexing
service, reporting interface, file generator)
4.6.8 Test enforcement of application entry points (OTG-AUTHZ-008) (including exposure of objects)
4.6.9 Testing for failure to restrict access to authenticated resource (OTG- AUTHZ-009)
4.7.6 Test Session Token Strength (OTG-SESS-006)
4.7.7 Testing for logout functionality (OTG-SESS-007)
4.7.8 Testing for Session puzzling (OWASP-SM-008)
4.7.8 Test Session Timeout (OTG-SESS-008)
4.7.9 Test multiple concurrent sessions (OTG-SESS-009)
4.8.5 Testing for Unvalidated Redirects and Forwards (OTG-INPVAL-005)
Testing for Remote File Inclusion
Testing for Cacheable HTTPS Response (OTG-CRYPST-004)
Test Cache Directives (OTG-CRYPST-005)
Testing for Insecure Cryptographic Storage (OTG-CRYPST-006)
Testing for Sensitive information sent via unencrypted channels (OTG-CRYPST-007)
Test Cryptographic Key Management (OTG-CRYPST-008)
WS Information Gathering (OTG-WEBSVC-002)
WS Authentication Testing (OTG-WEBSVC-003)
WS Management Interface Testing (OTG-WEBSVC-004)
Weak XML Structure Testing (OTG-WEBSVC-005)
XML Content-Level Testing (OTG-WEBSVC-006)
WS HTTP GET Parameters/REST Testing (OTG-WEBSVC-007)
WS Naughty SOAP Attachment Testing (OTG-WEBSVC-008)
WS Replay/MiTM Testing (OTG-WEBSVC-009)
WS BEPL Testing (OTG-WEBSVC-010)
Please contact Andy Muller