AI2.4:: Difference between revisions

From HORSE - Holistic Operational Readiness Security Evaluation.
Jump to navigation Jump to search
No edit summary
 
No edit summary
 
Line 1: Line 1:
'''AI 2.5 Configuration and Implementation of Acquired Application Software'''<br>
'''AI 2.4 Application Security and Availability'''<br>
<br>
<br>
'''Control Objective:'''<br>
'''Control Objective:'''<br>
<br>
<br>
Customize and implement acquired automated functionality using configuration, acceptance and testing procedures. Issues to consider include validation against contractual terms, the organization’s information architecture, existing applications, interoperability with existing application and database systems, system performance efficiency, documentation and user manuals, integration and system test plans.<br>  
Address application security and availability requirements in response to identified risks, in line with data classification, the organization’s information security architecture and risk profile. Issues to consider include access rights and privilege management, protection of sensitive information at all stages, authentication and transaction integrity, and automatic recovery.<br>  
<br>
<br>
'''Applicability:'''<br>
'''Applicability:'''<br>
Line 19: Line 19:
'''Risk Association Control Activities:'''<br>
'''Risk Association Control Activities:'''<br>
<br>
<br>
::'''1. Risk: Business requirements are not met or inadequately tested. Systems produce inaccurate results or do not meet usability requirements. A project that does not meet business requirements for internal controls at a milestone may continue without review and approval.'''<br>
::'''1. Risk: Users may have inappropriate access to the application system.'''<br>
:::a. SOX.1.2: Project management should ensure appropriate control over the design and implementation of new applications.<br>
:::a. SOX.5.1.1: Access to the application system is appropriately restricted to prevent unauthorized activity.<br>
<br>
::'''2. Risk: The impact of application system changes (e.g., hardware and software) should be evaluated and adjusted to ensure ongoing availability, performance and resilience requirements.'''<br>
:::a. SOX.6.1.1: The impact of application system changes (e.g., hardware and software) should be evaluated and adjusted to ensure ongoing availability performance and resilience requirements.<br>
<br>
<br>
'''Implementation Guide:'''<br>
'''Implementation Guide:'''<br>

Latest revision as of 15:05, 3 May 2006

AI 2.4 Application Security and Availability

Control Objective:

Address application security and availability requirements in response to identified risks, in line with data classification, the organization’s information security architecture and risk profile. Issues to consider include access rights and privilege management, protection of sensitive information at all stages, authentication and transaction integrity, and automatic recovery.

Applicability:

Sarbanes-Oxley
HIPAA
GLBA
PCI
FISMA
NIST SP 800-66
Ditscap
Control Exception
User Defined


Risk Association Control Activities:

1. Risk: Users may have inappropriate access to the application system.
a. SOX.5.1.1: Access to the application system is appropriately restricted to prevent unauthorized activity.


2. Risk: The impact of application system changes (e.g., hardware and software) should be evaluated and adjusted to ensure ongoing availability, performance and resilience requirements.
a. SOX.6.1.1: The impact of application system changes (e.g., hardware and software) should be evaluated and adjusted to ensure ongoing availability performance and resilience requirements.


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.

Retrieved from "http://horseproject.wiki/index.php?title=AI2.4:&oldid=1573"