Search results

Jump to navigation Jump to search
  • ...der to avoid unacceptable consequences associated with a break in business continuity. ...near the RTO. This would include alternate or manual workaround procedures and would not necessarily require computer systems to meet the RTOs.
    2 KB (272 words) - 11:15, 27 October 2012
  • ...used in this context are "Recovery Consistency Characteristics" (RCC) and "recovery object granularity" (ROG). ...n actual and targeted state of business data across systems for individual business processes or process groups.
    2 KB (313 words) - 11:24, 27 October 2012
  • '''Recovery Time Actual (RTA)''' is used in conjunction with RTO. ...plementation that reflects the recovery time frame that is required by the business.
    2 KB (237 words) - 11:16, 27 October 2012
  • ...d hot sites. The differences between the types are determined by the costs and effort required to implement each. ...ter to have the operation running at a capacity close to that prior to the disaster.
    5 KB (785 words) - 11:34, 27 October 2012
  • ...n (BSI)'s standard in the field of [[Business continuity planning|Business Continuity Management]] (BCM). This standard replaces PAS 56, a publicly available spe BS 25999 is a Business Continuity Management (BCM) standard published by the British Standards Institution (B
    7 KB (1,040 words) - 10:48, 27 October 2012
  • [[Image:BCPLifecycle.gif|Business continuity planning life cycle]] ...orm or a crime. In the US, governmental entities refer to the process as ''continuity of operations planning'' (COOP).
    15 KB (2,046 words) - 11:39, 27 October 2012
  • A “recovery point objective” or “RPO”, is defined by [[business continuity planning]]. It is the maximum tolerable period in which data might be lost ...common mistakes around the use and definition of RPO. First, staff use a [[business impact analysis]] to determine RPO for each service. RPO is NOT determined
    13 KB (2,264 words) - 11:10, 27 October 2012
  • ...ocessing, storage, and transmission of information or data and the systems and processes used for those purposes. While focused dominantly on information ...e practice of [[information security]] which in turn grew out of practices and procedures of [[computer security]].
    7 KB (983 words) - 10:41, 15 April 2012
  • ...ing both the probability of that event as the Single Loss Expectancy (SLE) and the resulting impact of the occurrence, otherwise known as the Annualized L ...rcial enterprise, the processes of calculating the cost of a risk exposure and what the appropriate costs of mitigating those risks should be.<br>
    23 KB (3,630 words) - 10:19, 27 October 2012
  • ...ysical or legal causes (e.g. natural disasters or fires, accidents, death, and lawsuits). ...sible approach to IT security risk management and may be found here: Risky Business: [[IT Security Risk Management Demystified]]
    43 KB (6,368 words) - 11:22, 4 July 2015