AI2.2:: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''AI 2. | '''AI 2.2 Detailed Design'''<br> | ||
<br> | <br> | ||
'''Control Objective:'''<br> | '''Control Objective:'''<br> | ||
<br> | <br> | ||
Prepare detailed design and technical software application requirements. Define the criteria for acceptance of the requirements. Have the requirements approved to ensure they correspond to the high-level design. Items to consider include, but are not limited to, input requirement definition and documentation, interface definition, user interface, source data collection design, program specification, file requirements definition and documentation, processing requirements, output requirement definition, control and audit ability, security and availability, and testing. Perform a [[Information_Security_Audit | security audit]] reassessment when significant technical or logical discrepancies occur during development or maintenance.<br> | |||
<br> | <br> | ||
'''Applicability:'''<br> | '''Applicability:'''<br> | ||
<br> | <br> | ||
:: | :: Sarbanes-Oxley | ||
:: HIPAA | :: HIPAA | ||
:: GLBA | :: GLBA | ||
| Line 18: | Line 18: | ||
<br> | <br> | ||
'''Risk Association Control Activities:'''<br> | '''Risk Association Control Activities:'''<br> | ||
<br> | <br> | ||
'''Implementation Guide:'''<br> | '''Implementation Guide:'''<br> | ||
Latest revision as of 13:35, 6 March 2007
AI 2.2 Detailed Design
Control Objective:
Prepare detailed design and technical software application requirements. Define the criteria for acceptance of the requirements. Have the requirements approved to ensure they correspond to the high-level design. Items to consider include, but are not limited to, input requirement definition and documentation, interface definition, user interface, source data collection design, program specification, file requirements definition and documentation, processing requirements, output requirement definition, control and audit ability, security and availability, and testing. Perform a security audit reassessment when significant technical or logical discrepancies occur during development or maintenance.
Applicability:
- Sarbanes-Oxley
- HIPAA
- GLBA
- PCI
- FISMA
- NIST SP 800-66
- Ditscap
- Control Exception
- User Defined
Risk Association Control Activities:
Implementation Guide:
Process Narrative
Insert a description of the process narration that is applicable to the existing control statement this narrative refers to.
Process Illustration
Insert a process diagram, flowchart or other visual representation here to illustrate the process narrative.
File:Someimage.jpg
Control Commentary
Insert a description of the control that is applicable to the existing control statement this commentary refers to.
Control Exception Commentary
Insert a description of the control exception that is applicable to the existing control statement this commentary refers to.
Evidence Archive Location
Insert Evidence Description Here.
Control Status and Auditors Commentary
Describe the condition of the applicable control and its effectiveness. Set the color icon to a redlock.jpg, yellowlock.jpg or greenlock.jpg.
File:Redlock.jpg
Remediation Plan
Insert remediation plan, applicability, or any information that indicates what needs to be done.
Supplemental Information:
Implementation guidance
Insert guidance in this section if it helps to elaborate upon the subject matter. Examples of evidence that would help guide the end user is desirable.