A software fault prevents the proper and reliable use of an application or feature, although reputable software and correct procedures have been used. A software incident becomes a 'fault' when the investigator has disproved other factors, such as user error. An 'incident' is an unexpected event or result which in itself may be minor but may be symptomatic of a larger problem or may signal an actual or potential security breach. All incidents must be taken seriously.

• Errors are compounded due to delays in fault or incident reporting.

There is 1 Key Action providing safeguards against this Information Security Issue. These are available in the registered version of RUSecure™.

• Insufficient data may lead to incorrect diagnosis of the fault or may hide a possible security breach.

There are 2 Key Actions providing safeguards against this Information Security Issue. These are available in the registered version of RUSecure™.

• Where there are no procedures to monitor reported faults or to undertake trend analysis, the underlying source of the problem may go undetected.

There is 1 Key Action providing safeguards against this Information Security Issue. These are available in the registered version of RUSecure™.

• No procedures in place to handle software fault reporting.

There are 2 Key Actions providing safeguards against this Information Security Issue. These are available in the registered version of RUSecure™.

• Lack of any proactive preventative maintenance.

There is 1 Key Action providing safeguards against this Information Security Issue. These are available in the registered version of RUSecure™.