Business Expiration Needs

13,809 views

Published on

Foundations of Information Security: Expiration

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
13,809
On SlideShare
0
From Embeds
0
Number of Embeds
11,222
Actions
Shares
0
Downloads
23
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Business Expiration Needs

  1. 1. ExpirationFoundations of Information Security Series Vicente Aceituno @vaceituno (c)Inovement Europe 2014
  2. 2. Vicente Aceituno vac@zenobia.es - Skype: vaceituno Linkedin - linkedin.com/in/vaceituno Inovement Europe - inovement.es Video Blog - youtube.com/user/vaceituno Blog - ism3.com Twitter - twitter.com/vaceituno Presentations - slideshare.net/vaceituno/presentations Articles - slideshare.net/vaceituno/documents
  3. 3. Foundations of Information Security Series  Needs  Secrecy  Intellectual Property you Own  Intellectual Property you Use  Privacy  Availability  Retention  Expiration  Quality  Obligations  Technical  Compliance  Legal
  4. 4. What is Information Security?  “Information Security” is an emergent property of people using information.  People have expectations about information.  If there is no people or no information, “Information Security” is meaningless, as there are no expectations to meet.
  5. 5. What is Information Security?  When expectations about information are met, there is “Security”.  When expectations about information are not met, there is an “Incident”.
  6. 6. What is Information Security?  Some expectations are things people (or organizations) want to happen for their own reasons. These are Needs.  Some expectations are things people (or organizations) want to happen in order to meet technical, legal or standard compliance requirements. These are Obligations.
  7. 7. Expiration
  8. 8. Expiration  Some expectations of people about information are related to ownership, control and use of information over time.
  9. 9. Expiration  Ownership is defined having legal rights and duties on something.  Control is defined as having the ability to:  Grant or deny access to users.  Attribute to specific users their use of information.  Use is defined as having access to read, write or modify information.
  10. 10. Expiration  There is an expectation that information will be controlled by their owners or authorized administrators only, for as long as they are authorized.  There is an expectation that information will be used by authorized users only, for as long as they are authorized.
  11. 11. Expiration  If these expectations are met or not is independent of the observer and repeatable.  Expiration expectations can be determined answering the following question:  Under what circumstances should the information be destroyed? (Example: Information system sent to the dealer for maintenance)  When should the information be destroyed? When does this length of time start counting?  Answering these question renders requirements that can managed.
  12. 12. Expiration related incidents  When information can be controlled or used after the expected length of time. For a more complete list of incidents check tiny.cc/incidents
  13. 13. Achieving Expiration  In order to achieve Expiration, normally information is overwritten with random information.  The directly related O-ISM3 process is:  OSP-6: IT Managed Domain Clearing  Having multiple copies of information makes it less likely that Expiration expectations are met.
  14. 14. Expiration
  15. 15. The O-ISM3 Challenge  This was an exercise designed to throw into sharp relief the inadequacy of traditional information security concepts.  Check the exercise in full at tiny.cc/indepth  A summary of conclusions from the exercise, in relation to Expiration, follow.
  16. 16. Secrecy Business Needs Intellectual Property Privacy Integrity Business Obligations Integrity Availability Retention Quality Expiration
  17. 17. Integrity  ISO Definition: The property of safeguarding the accuracy and completeness of assets.  ITIL Definition: A security principle that ensures data and Configuration Items are only modified by authorized personnel and Activities. Integrity considers all possible causes of modification, including software and hardware Failure, environmental Events, and human intervention.  CobIT Definition: Relates to the accuracy and completeness of information as well as to its validity in accordance with business values and expectations.
  18. 18. Expiration and Integrity  Integrity can’t be measured (it doesn’t have units). Therefore is not independent of the observer nor repeatable like Expiration is.  Expiration can be used to measure, communicate and manage a specific expectation of people about information.  Integrity is not necessary to understand or measure Expiration.
  19. 19. Expiration and Integrity  Expiration and Integrity are not equivalent.  Integrity and Expiration are not synonymous.  Integrity is not useful to understand Expiration.
  20. 20.  Follow the Foundations of Information Security Series by joining the Linkedin O-ISM3 Group at: tiny.cc/osim3LG  Learn Advanced Information Security Management, joining us at an O-ISM3 Course: tiny.cc/osim3

×