This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Use encapsulation"
From OWASP
m (Encapsulation moved to Use encapsulation) |
|||
| Line 7: | Line 7: | ||
==Examples == | ==Examples == | ||
* Design: Separate internal administrator's functions from external users' functions | * Design: Separate internal administrator's functions from external users' functions | ||
| − | * Implementation: | + | * Implementation: Hide internal details of a class, including data and methods, using private access modifier. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 14:46, 14 June 2006
This is a principle or a set of principles. To view all principles, please see the Principle Category page.
Description
Draw strong boundaries among application elements, including modules, functions and data, to limit the impact of potential attacks.
Examples
- Design: Separate internal administrator's functions from external users' functions
- Implementation: Hide internal details of a class, including data and methods, using private access modifier.
