* Johan Peeters: > while I am being persuaded that you can use input validation and > output encoding interchangeably
Interchangeably? Hardly. > as countermeasures for *some* problems documented here, there is > another important dimension: enforcement of business rules. In this > domain, I do not see an alternative to input validation. What is a business rule? Something like "If the customer has changed the shipment address from a previous order, we must re-request his or her credit card details"? How would you implement *that* using input validation? _______________________________________________ Secure Coding mailing list (SC-L) SC-L@securecoding.org List information, subscriptions, etc - http://krvw.com/mailman/listinfo/sc-l List charter available at - http://www.securecoding.org/list/charter.php SC-L is hosted and moderated by KRvW Associates, LLC (http://www.KRvW.com) as a free, non-commercial service to the software security community. _______________________________________________
