Security guidelines for Expertiza: Difference between revisions
Jump to navigation
Jump to search
(Created page with "==Security Guidelines== Web applications such as Expertiza present a complex set of security issues for users, designers, and developers. The most secure and hack-resilient Web ...") |
No edit summary |
||
| Line 5: | Line 5: | ||
In addition to applying sound architectural and design practices, incorporate deployment considerations and corporate security policies during the early design phases. Failure to do so can result in applications that cannot be deployed on an existing infrastructure without compromising security. | In addition to applying sound architectural and design practices, incorporate deployment considerations and corporate security policies during the early design phases. Failure to do so can result in applications that cannot be deployed on an existing infrastructure without compromising security. | ||
This guideline presents a set of secure architecture and design guidelines we have followed to ensure that Expertiza is designed with security it's core. | This guideline presents a set of secure architecture and design guidelines we have followed to ensure that Expertiza is designed with security at it's core. | ||
Revision as of 14:50, 2 May 2018
Security Guidelines
Web applications such as Expertiza present a complex set of security issues for users, designers, and developers. The most secure and hack-resilient Web applications are those that have been built from the ground up with security in mind.
In addition to applying sound architectural and design practices, incorporate deployment considerations and corporate security policies during the early design phases. Failure to do so can result in applications that cannot be deployed on an existing infrastructure without compromising security.
This guideline presents a set of secure architecture and design guidelines we have followed to ensure that Expertiza is designed with security at it's core.