Protecting software systems

Protecting software systems

1. Software design stage

   • The software designers will need to consider:
     • What kind of authentication is needed?
     • Will access control be needed?
     • Are warnings needed before allowing users to copy or delete large amounts of information.
     • Is encryption needed for sensitive information?
     • Will the software be exposed to threats from hackers?

2. Modular testing

   • A module is an independent block of code that implements a small number of routines. As only a small amount is being tested, any problems should be easier to fix.

3. Audit trails - audit software

   • Can monitor all network activity and keep a record of all user activity - their audit trail. It allows a technician to study what has happened during a cyberattack.

4. Vulnerabilities in coding the program

   • Code vulnerabilities - When the code does the task intended but, due to the way it works, it may create a security issue in some cinrcumstances.
   • Bad coding practice - Some programmers write poor-quality code and don't consider how safe or secure their code is.

5. Effective network security provision

   • Users must receive training and be aware of the security threats.
   • Network administrators and technical staff should:
     • Receive on-going training
     • Ensure that all operating system updates and software patches are applied.

6. Securing operating systems

   • There are security vulnerabilities in all operating systems and as these are identified, they should be removed by installing updates.