L4 - Code Integrity and Handling

L4 - Code Integrity and Handling

1. Code Integrity

   • It is a measurement used in s/w testing
   • It measure how high the code's quality is when passed to QA
   • Releases:
     • Better product
     • fewer bugs
     • Shorter time
   • How to improve code integrity?
     • Unit testing the code
     • Integration testing the code
     • Assigning a code to an integrity manager
   • Advantages:
     • Shorter development time
       • Bugs found faster thus corrected faster
     • Lower development cost
       • Cheaper to correct bug in early stages than later in SDLC
     • Confidence in code's quality
       • Release product with high integrity means customer satisfaction.
     • Makes QA more efficient

2. Practices

   • Least Privilege Access
     • In a particular abstraction layer of a computing environment, every module must be able to access only information and resources that are appropriate.
   • Persistent Protection
     • Critical data is protected in ways that remain effective
     • Code should be protected while active, at rest and in transit.
   • Separation Of duties
     • Distribution of tasks and associative proiviledges for a specific security process.
     • Ojectives:
       • Prevention of conflicts
       • Detection of control failures.
   • Compliance Management
     • The process which ensures that a set of people are following a given set of rules.
   • Chain of Custody
     • Detailed, chronological record of how data was retrieved, manipulated and transfered.
     • meta data of data
     • shows where evidence has been.