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 "Talk:Industry:Project Review/NIST SP 800-37r1 FPD Appendix D"
(→D.11 INFORMATION SECURITY ARCHITECT) |
Ryan Trost (talk | contribs) (→D.2 RISK EXECUTIVE (FUNCTION)) |
||
| Line 16: | Line 16: | ||
== D.2 RISK EXECUTIVE (FUNCTION) == | == D.2 RISK EXECUTIVE (FUNCTION) == | ||
It seems that so far, no one role is specifically required or has the objective to define one or more organizational methods for risk calculation. From personal experience, it is too easy to ignore one risk set in deference for another because of professional unfamiliarity with the first. An objective risk calculation toolset defined by organizational management provides a framework for first identifying risk, then prioritizing the addressing of risks. | It seems that so far, no one role is specifically required or has the objective to define one or more organizational methods for risk calculation. From personal experience, it is too easy to ignore one risk set in deference for another because of professional unfamiliarity with the first. An objective risk calculation toolset defined by organizational management provides a framework for first identifying risk, then prioritizing the addressing of risks. | ||
| + | |||
| + | [User: Ryan] Minor suggestion: move the last bullet point re: shared responsibility up one (to keep shared responsibility bullets together). | ||
| + | |||
| + | [User: Ryan] The sheer size of some of these sentences is painful. Although correct...it inevitably forces me to re-read them several times. | ||
== D.3 CHIEF INFORMATION OFFICER == | == D.3 CHIEF INFORMATION OFFICER == | ||
Revision as of 20:55, 21 December 2009
APPENDIX D
ROLES AND RESPONSIBILITIES
KEY PARTICIPANTS IN THE RISK MANAGEMENT PROCESS
D.1 HEAD OF AGENCY (CHIEF EXECUTIVE OFFICER)
D.2 RISK EXECUTIVE (FUNCTION)
It seems that so far, no one role is specifically required or has the objective to define one or more organizational methods for risk calculation. From personal experience, it is too easy to ignore one risk set in deference for another because of professional unfamiliarity with the first. An objective risk calculation toolset defined by organizational management provides a framework for first identifying risk, then prioritizing the addressing of risks.
[User: Ryan] Minor suggestion: move the last bullet point re: shared responsibility up one (to keep shared responsibility bullets together).
[User: Ryan] The sheer size of some of these sentences is painful. Although correct...it inevitably forces me to re-read them several times.
D.3 CHIEF INFORMATION OFFICER
D.4 INFORMATION OWNER/STEWARD
D.5 SENIOR INFORMATION SECURITY OFFICER
D.6 AUTHORIZING OFFICIAL
D.7 AUTHORIZING OFFICIAL DESIGNATED REPRESENTATIVE
D.8 COMMON CONTROL PROVIDER
D.9 INFORMATION SYSTEM OWNER
D.10 INFORMATION SYSTEM SECURITY MANAGER/OFFICER
D.11 INFORMATION SECURITY ARCHITECT
Placing the Information Security Architect at the level of system-specific personnel, but ascribing to the position "requirements to protect the organization's core mission and business processes" is a grave mistake. This is confusing in that the System Owner and ISSO duties are specific to the level of the system with an eye toward the overall organization/agency/nation. This description needs to be re-addressed to better discuss the role at the system level.
