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 "Top 10-2017 What's Next for Application Managers"
(OWASP Top 10-2017 Release (Content based on Markdown)) |
m (Editorial Change: moved 'change management data base (CMDB)' to 'Deployment, Testing, and Rollout') |
||
Line 38: | Line 38: | ||
* Manage security tests according to internal processes, the protection needs, and the assumed threat level by the application. | * Manage security tests according to internal processes, the protection needs, and the assumed threat level by the application. | ||
* Put the application in operation and migrate from previously used applications if needed. | * Put the application in operation and migrate from previously used applications if needed. | ||
− | * Finalize all documentation, including the CMDB and security architecture. | + | * Finalize all documentation, including the change management data base (CMDB) and security architecture. |
{{Top 10:GrayBoxEnd|year=2017}} | {{Top 10:GrayBoxEnd|year=2017}} | ||
{{Top_10:GradientBox|year=2017}} | {{Top_10:GradientBox|year=2017}} | ||
Line 45: | Line 45: | ||
* Raise the security awareness of users and manage conflicts about usability vs. security. | * Raise the security awareness of users and manage conflicts about usability vs. security. | ||
* Plan and manage changes, e.g. migrate to new versions of the application or other components like OS, middleware, and libraries. | * Plan and manage changes, e.g. migrate to new versions of the application or other components like OS, middleware, and libraries. | ||
− | * Update all documentation, including in the | + | * Update all documentation, including in the CMDB and the security architecture, controls, and countermeasures, including any runbooks or project documentation. |
{{Top 10:GrayBoxEnd|year=2017}} | {{Top 10:GrayBoxEnd|year=2017}} | ||
{{Top_10:GradientBox|year=2017}} | {{Top_10:GradientBox|year=2017}} |
Latest revision as of 17:31, 1 January 2018
Manage the Full Application Lifecycle
Applications belong to the most complex systems humans regularly create and maintain. IT management for an application should be performed by IT specialists who are responsible for the overall IT lifecycle of an application. We suggest establishing the role of application manager as technical counterpart to the application owner. The application manager is in charge of the whole application lifecycle from the IT perspective, from collecting the requirements until the process of retiring systems, which is often overlooked.
Requirements and Resource Management
Request for Proposals (RFP) and Contracting
Planning and Design
Deployment, Testing, and Rollout
Operations and Change Management
Retiring Systems
|
![CC-by-sa-3 0-88x31.png](/images/6/64/CC-by-sa-3_0-88x31.png)