1. Presented by: Nick McHugh Date: 15/11/2005 Security, Safety, Confidence

2. Agenda Data – the need for security Data security within QAS solutions QAS Integrations – ensuring they are safe Making your solution safe Summary

3. The need for security QAS BS7799 (ISO17799) Collection and dissemination Processed Managed, transferred and stored Data Protection Act

4. Data – why it must be secure Sensitive data >18 suppliers of data Data not ours Sharing Contractual obligations What you can do with it Who can use it

5. Security within QAS solutions Data Binary format

6. Names data file

7. Security within QAS solutions Data Binary format Can’t modify it Can’t read it Access only through QAS products Standalone & APIs License control Data level

8. Ensuring integrations are safe Risk 3 rd party software Internal standards Support, SLA Your responsibility Error handling Correct logic Threading Loose Vs strong coupling

9. Making your solution safe Ask for help Speak to us Web site Manuals, tech notes, sample code QAS accreditation Assess integration Technical & functional perspective Recommend changes Document set up

10. QAS integration service Assist or undertake integrations Experts Planning & coding Reduces integration time Migration services Training Making your solution safe

11. Summary Security Confidence in supplier Contractual obligations QAS security Safety Ensuring your solution is safe Assistance from QAS