While we can all agree on the importance of protecting information and information systems, it’s much harder to agree on how we define the state of being secure. Is it the state where all information security risks are completely eliminated (not possible)? Is it the state where all security risks are mitigated to an acceptable level (which risks and whose definition of acceptable)? Even if we reach consensus and achieve the agreed upon state – we all understand that it is fleeting and will only last until a change (often outside of our control) denigrates it.
It is because the assurance we receive is often only valid at an “instant in time” (e.g., a penetration test) that trust is so important. If we don’t trust that the person/team/organization responsible to ensure critical information is handled in the manner we aspire to moving forward, then we really have little or no assurance.
We were recently engaged by a pharmaceutical firm to assess whether a third party developed and hosted implementation of a multi-million dollar clinical trials solution achieved the security objectives defined in the contract. The report would also form the basis of a new contract intended to “remedy” the existing challenges.
The meeting took a very interesting turn when I asked “Should we really be discussing a new contract when it is obvious that the service provider has proven they are not trustworthy?” (the impact of the vendor failing to achieve critical security objectives could cost the pharmaceutical tens of millions)
For my money, no contract, no matter how carefully worded, will make a company trustworthy. And without trust we have no confidence/assurance that critical information will remain secure.
Related Articles That Might Interest You
Is ISO 27001 Right for (Y)our Organization?
Thinking about ISO 27001 Certification? View our free On-Demand ISO 27001 Webinar
- How to deal with increasing threats
- How to manage multiple regulatory requirements
- How to handle client requests for attestation
- To validate that significant changes did not have unanticipated results
Free Whitepaper: Stop Wasting Money on Penetration Testing
Penetration Testing is most frequently performed to:
- Substantiate the net effectiveness of a mature control environment
- Prove to a third party that an environment is secure/trustworthy
- Quickly assess the security of a less mature control environment (in a sense a technical risk assessment)
- To validate that significant changes did not have unanticipated results
Free Download: A Best Practices Guide to Database Security
Because data is only as secure as the systems & processes it relies on – a holistic approach to data security is essential. This roadmap is not meant to be exhaustive but rather to stimulate the necessary thought process to put you on the path to good data security.
Download: Information Security Attestation Guide
A Best-Practices Guide to Information Security Attestation
Download our proven Information Security Guide to simplify the process of protecting your data, proving you’re secure and growing your business.
Free Whitepaper: Five Best Practices for SIEM
The promise of SIEM is the consolidation of all relevant Security Event Logs from disparate sources into a single unified and normalized data store.
Free Download: ISO 27001 Implementation Roadmap
Have no fear – our “roadmap” will guide you, step by step, through the entire ISO 27001 process.
Getting to ISO 27001 certification is a process made up of things you already know – and things you may already be doing!
About the Author:
John W. Verry, CISA/27001 Lead Auditor/CCSE/CRISC - "Security Sherpa" - Information Security Auditor