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
Weilin Zhong (talk | contribs) |
Weilin Zhong (talk | contribs) |
||
| Line 6: | Line 6: | ||
==Examples == | ==Examples == | ||
| + | * Design: Separate internal administrator's functions from external users' functions | ||
| + | * Implementation: Hidde internal details of a class, including data and methods, using private access modifier. | ||
| + | |||
| + | ==Related Principles== | ||
==Related Threats== | ==Related Threats== | ||
Revision as of 17:57, 9 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: Hidde internal details of a class, including data and methods, using private access modifier.
Related Principles
Related Threats
Related Attacks
Related Vulnerabilities
Related Countermeasures
Categories
This article is a stub. You can help OWASP by expanding it or discussing it on its Talk page.
