Search results

Jump to navigation Jump to search
View (previous 50 | ) (20 | 50 | 100 | 250 | 500)
  • ...is also the responsibility of Release Management. This guarantees that all software can be conceptually optimized to meet the demands of the business processes *Plan to rollout of software ...
    2 KB (352 words) - 16:42, 20 March 2007
  • ...are fixed via vendor security patches, and all systems should have current software patches to protect against exploitation by employees, external hackers, and ...re that all system components and software have the latest vendor-supplied security patches.'''<br> ...
    4 KB (578 words) - 18:46, 28 February 2007
  • '''Secure by design''', in software engineering, means that the program in question has been designed from the ...years of testing and debugging, and while they may provide a great deal of security, they typically have no way to guarantee that a new bug or exploit won't be ...
    2 KB (343 words) - 18:39, 14 June 2007
  • ...also create risk that can be in the form of more rework than anticipated, security holes, and privacy invasions (Messerschmitt and Szyperski, 2004).<br> ...the potential customer base, specialization risk can be significant for a software firm. After probabilities of scenarios have been calculated with risk analy ...
    1 KB (215 words) - 18:32, 13 April 2007
  • ...Unix and Linux systems. This may involve, among other measures, applying a software patch to the kernel such as Exec Shield or PaX; closing open TCP and UDP po *[[Computer security]] ...
    1 KB (168 words) - 18:26, 14 June 2007
  • ...ver authorization, authentication, nonrepudiation, data classification and security monitoring may result in inaccurate financial reporting.''' ...security standards has been developed that supports the objectives of the security policy. ...
    3 KB (360 words) - 16:59, 25 June 2006
  • ...'']] IT management implements system software that does not jeopardize the security of the data and programs being stored on the system. ...ermine that a risk assessment of the potential impact of changes to system software is performed. ...
    2 KB (303 words) - 19:58, 23 June 2006
  • ...de a comprehensive framework for ensuring the effectiveness of information security controls over information resources that support Federal operations and ass ...dination of information security efforts throughout the civilian, national security, and law enforcement communities;<br> ...
    1 KB (192 words) - 10:33, 1 June 2010
  • ...de a comprehensive framework for ensuring the effectiveness of information security controls over information resources that support Federal operations and ass ...dination of information security efforts throughout the civilian, national security, and law enforcement communities;<br> ...
    1 KB (192 words) - 10:36, 1 June 2010
  • ::'''2. Risk: Insufficient configuration controls can lead to security and availability exposures that may permit unauthorized access to systems a :::a. [[SOX.2.0.29:|'''SOX.2.0.29''']] Only authorized software is permitted for use by employees using company IT assets.<br> ...
    2 KB (314 words) - 18:27, 25 June 2006
  • ...hich are used to access the organization’s network, have personal firewall software installed and active.'''<br> ...oint firewall and security software configurations to verify that security software standards are acceptable and that updates are current prior to authorizing ...
    2 KB (296 words) - 10:57, 16 June 2010
  • ...lopment processes to confirm they are based on industry standards and that security is included throughout the life cycle.<br> :From review of written software development processes, inquiry of software developers, and review of relevant data (network configuration documentatio ...
    2 KB (298 words) - 18:26, 28 February 2007
  • ...e cycle. From review of written software development processes, inquiry of software developers, and review of relevant data (network configuration documentatio ...
    2 KB (297 words) - 18:33, 28 February 2007
  • '''10. Risk: Reactive security monitoring results in data compromise and financial loss or liability.'''<b :a. SOX.4.2.1.10: UNIX administration team is notified when security violations occur.<br> ...
    3 KB (421 words) - 20:20, 12 June 2006
  • ...e cycle. From review of written software development processes, inquiry of software developers, and review of relevant data (network configuration documentatio ...
    2 KB (304 words) - 18:36, 28 February 2007
  • '''Zero day''' in technology refers to software, videos, music, or information unlawfully released or obtained on the day o ===Software=== ...
    4 KB (570 words) - 19:02, 14 June 2007
  • ...e cycle. From review of written software development processes, inquiry of software developers, and review of relevant data (network configuration documentatio ...
    2 KB (307 words) - 18:29, 28 February 2007
  • ...e cycle. From review of written software development processes, inquiry of software developers, and review of relevant data (network configuration documentatio ...
    2 KB (304 words) - 18:28, 28 February 2007
  • ...e cycle. From review of written software development processes, inquiry of software developers, and review of relevant data (network configuration documentatio ...
    2 KB (316 words) - 18:30, 28 February 2007
  • '''AI 2.10 Application Software Maintenance'''<br> ...ort issues and upgrades, periodic review against business needs, risks and security requirements.<br> ...
    6 KB (878 words) - 13:34, 23 June 2006
  • ...ist of security patches installed on each system to the most recent vendor security patch list, to determine that current vendor patches are installed.<br> ...ch installation to determine they require installation of all relevant new security patches within 30 days.<br> ...
    2 KB (295 words) - 18:20, 28 February 2007
  • ...e cycle. From review of written software development processes, inquiry of software developers, and review of relevant data (network configuration documentatio ...
    2 KB (334 words) - 18:37, 28 February 2007
  • == Requirement 11: Regularly test security systems and processes. == ...tems, processes, and custom software should be tested frequently to ensure security is maintained over time and through changes. ...
    3 KB (372 words) - 17:59, 7 July 2006
  • '''DS 5.7 Protection of Security Technology '''<br> ...ow profile. However, do not make security of systems reliant on secrecy of security specifications. ...
    3 KB (377 words) - 18:52, 4 May 2006
  • ::'''1. Risk: Insufficient configuration controls can lead to security and availability exposures that may permit unauthorized access to systems a ...0.32''']] Periodic testing and assessment is performed to confirm that the software and network infrastructure is appropriately configured. ...
    2 KB (288 words) - 18:53, 25 June 2006
  • '''Sustainable Risk Reduction Through Information Security Process Awareness Test Template.'''<br> ...> to gauge and promote end-user awareness of managing risk with the use of security processes.<br> ...
    2 KB (305 words) - 17:31, 3 August 2006
  • '''Sustainable Risk Reduction Through Information Security Process Awareness Test Template.'''<br> ...> to gauge and promote end-user awareness of managing risk with the use of security processes.<br> ...
    2 KB (309 words) - 17:34, 3 August 2006
  • What are assets? Asset Management from a corporate governance and information security perspective is not just about 'IT' Assets. It is about the management, cont ...is taken from and attributable to UK-National Health Services Information Security it I believe adequately covers what we can do/do with data. ...
    5 KB (705 words) - 13:29, 23 May 2007
  • ...otification message produced by the system being tested to verify that the security administrators are being proactively notified of possible access violations ...be a monitoring background process that sends an electronic message to the security administrative group automatically when root access occurs. The email messa ...
    3 KB (422 words) - 00:09, 13 June 2006
  • '''AI 2.4 Application Security and Availability'''<br> ...ed risks, in line with data classification, the organization’s information security architecture and risk profile. Issues to consider include access rights and ...
    3 KB (374 words) - 15:05, 3 May 2006
  • Controls provide reasonable assurance that IT components, as they relate to security, processing and availability, are well protected, would prevent any unautho :5. Prevent the inclusion of unauthorized software ...
    3 KB (429 words) - 18:55, 25 June 2006
  • ...cilities, technology, and user procedures) and ensure that the information security requirements are met by all components. The test data should be saved for a ISO 17799 12.1 Security requirements of information systems.<br> ...
    5 KB (730 words) - 19:05, 17 April 2007
  • '''AI 2.5 Configuration and Implementation of Acquired Application Software'''<br> Controls provide reasonable assurance that IT components, as they relate to security, processing and availability, are well protected, would prevent any unautho ...
    4 KB (501 words) - 18:24, 25 June 2006
  • ...controls)that are needed to create, implement, and maintain an Information Security Program that complies with ISO 17799.<br> :*'''[[Security Policy:|'''Security Policy''']]<br> ...
    8 KB (1,023 words) - 17:25, 24 October 2006
  • ...h management and upgrade strategies, risks, vulnerabilities assessment and security requirements.<br> ::'''2. Risk: The impact of application system changes (e.g., hardware and software) should be evaluated and adjusted to ensure ongoing availability, performan ...
    6 KB (819 words) - 13:54, 23 June 2006
  • =='''Sample Software Acceptable Use Standard'''== ...ons and requirements on the proper and appropriate business use of Company software.<br> ...
    7 KB (953 words) - 14:13, 1 May 2010
  • '''PO 4.8 Responsibility for Risk, Security and Compliance'''<br> ...es may need to be assigned at a system-specific level to deal with related security issues. Obtain direction from senior management on the appetite for IT risk ...
    3 KB (370 words) - 18:04, 1 May 2006
  • '''DS 5.9 Malicious Software Prevention, Detection and Correction '''<br> ...m malware (viruses, worms, spy-ware, spam, internally developed fraudulent software, etc.). ...
    8 KB (1,177 words) - 19:00, 25 June 2006
  • ==Security Audit Guidance== For security audit guidance, please refer to [[Audit_Guidance_Examination_Procedures | A ...
    5 KB (665 words) - 14:40, 11 April 2007
  • ==Security requirements of information systems== The objective of this category is to ensure that security is an integral part of the organization's information systems, and of the b ...
    9 KB (1,170 words) - 14:05, 22 May 2007
  • ==Personnel Security== ...rs grant legitimate users system access necessary to perform their duties; security personnel enforce access rights in accordance with institution standards. B ...
    10 KB (1,327 words) - 12:54, 10 April 2007
  • Controls provide reasonable assurance that IT components, as they relate to security, processing and availability, are well protected, would prevent any unautho ...ion on configuration items. This repository includes hardware, application software, middleware, parameters, documentation, procedures and tools for operating, ...
    4 KB (506 words) - 18:44, 25 June 2006
  • :'''Verify that the personal firewall software is configured by the organization to specific standards and is not alterabl :* Examine associated endpoint firewall and security software configurations to verify that administration is restricted only authorized ...
    2 KB (267 words) - 10:51, 16 June 2010
  • The objective of this category is to manage information security within the organization's overall administrative structure.<br> ===Management commitment to information security=== ...
    8 KB (996 words) - 12:49, 22 May 2007
  • ...ropriate into related groups or domains (e.g., hardware, software, support software). These groups may match the organizational responsibilities or the user an ::'''1. Risk: Security incidents and incompliance with information security procedures may go overlooked and not addressed.''' ...
    4 KB (601 words) - 15:01, 8 August 2006
  • ==Laws and regulations governing Information Security== ...have also been included when they have a significant impact on information security. ...
    4 KB (556 words) - 14:03, 8 March 2007
  • '''DS 11.6 Security Requirements for Data Management '''<br> Establish arrangements to identify and apply security requirements applicable to the receipt, processing, physical storage and ou ...
    5 KB (649 words) - 18:23, 5 May 2006
  • :'''Avoid Session Management Pitfalls:''' [[Media:session-management-security.pdf]]<br> ...Configuration Management for Security:''' [[Media:configuration-management-security.pdf]] <br> ...
    6 KB (839 words) - 16:22, 23 April 2007
  • ...t Protection Standard, Company protection standards shall include specific security requirements in the following areas: ## Sample Protection Standards must be reviewed by the Information Security Department to ensure vulnerabilities are not introduced into the Company pr ...
    5 KB (681 words) - 21:56, 15 January 2014
  • ...any change-control procedures related to implementing security patches and software modifications, and determine the procedures required.'''<br> ...ct a sample of system components and find the three most recent changes or security patches for each system component, and trace those changes back to related ...
    2 KB (307 words) - 18:42, 28 February 2007
View (previous 50 | ) (20 | 50 | 100 | 250 | 500)