Validating xml data
To ensure that the application is robust against all forms of input data, whether obtained from the user, infrastructure, external entities or database systems. This weakness leads to almost all of the major vulnerabilities in applications, such as Interpreter Injection, locale/Unicode attacks, file system attacks and buffer overflows.
All sections should be reviewed The most common web application security weakness is the failure to properly validate input from the client or environment.
Data from the client should never be trusted for the client has every possibility to tamper with the data.
Detecting attempts to find these weaknesses is a critical protection mechanism.For example, if you use HTML entity encoding on user input before it is sent to a browser, it will prevent most XSS attacks.However, simply preventing attacks is not enough - you must perform Intrusion Detection in your applications.int payee Lst Id = Parameter('payeelstid'); account From = Acct Number By Index(payee Lst Id); Not only is this easier to render in HTML, it makes validation and business rule validation trivial. To provide defense in depth and to prevent attack payloads from trust boundaries, such as backend hosts, which are probably incapable of handling arbitrary input data, business rule validation is to be performed (preferably in workflow or command patterns), even if it is known that the back end code performs business rule validation.
This is not to say that the entire set of business rules need be applied - it means that the fundamentals are performed to prevent unnecessary round trips to the backend and to prevent the backend from receiving most tampered data.
Here are some examples: If you expect a phone number, you can strip out all non-digit characters.