Focus Areas of ISO/IEC 27001:2013

Information security management system ISO 27001 (formerly known as ISO/IEC 27001:2005) specification (ISMS). The legal, physical, and technical controls involved in an organization’s information risk management processes are all part of an ISMS, which is a framework of rules and procedures. For the purpose of “providing a model for establishing, implementing, operating, monitoring, reviewing, maintaining and enhancing an information security management system,” ISO 27001 was created, according to its literature.

Technology-neutral and top-down, ISO 27001 follows a risk-based methodology. A six-step planning procedure is outlined in the specification:

  • Define a security policy.
  • Define the scope of the ISMS.
  • Conduct a risk assessment.
  • Manage identified risks.
  • Select control objectives and controls to be implemented.
  • Prepare a statement of applicability.

The specification includes details for documentation, management responsibility, internal audits, continual improvement, and corrective and preventive action. The standard requires cooperation among all sections of an organisation.

The 27001 standards does not mandate specific information security controls, but it provides a checklist of controls that should be considered in the accompanying code of practice, ISO/IEC 27002:2005. This second standard describes a comprehensive set of information security control objectives and a set of generally accepted good practice security controls.

ISO 27002 contains 12 main sections:

  1. Risk assessment
  2. Security policy
  3. Organization of information security
  4. Asset management
  5. Human resources security
  6. Physical and environmental security
  7. Communications and operations management
  8. Access control
  9. Information systems acquisition, development and maintenance
  10. Information security incident management
  11. Business continuity management
  12. Compliance

Organizations must implement these measures correctly in accordance with their unique risks. For ISO 27001 compliance, third-party recognized certification is advised. Organizations must implement these measures in a way that is appropriate for their particular risks. For compliance with ISO 27001, third-party authorized certification is advised.

GDPR: When should you obtain consent?

Knowing how to obtain consent under the General Data Protection Regulation (GDPR) and when to do so might be challenging. Many individuals wrongly believe that organisations must obtain consent before processing personal data however, consent is simply one of six legal justifications, and you should only use it if all other options have been exhausted.

Other acceptable grounds include:  A contract with the person, such as one under which obligations under an employment contract must be fulfilled or goods or services must be provided as per their desire. When processing data for a certain purpose is required by law, compliance is required. Vital interests, such as protecting someone’s physical integrity or life (either the data subject’s or another person’s), are examples of vital interests. An official function or duty that serves the public interest is an example of a public task. This often applies to public institutions including government agencies, educational institutions, hospitals, and the police.

Legitimate interests: When a private-sector organisation has a true and legitimate reason (including a financial profit) to process a person’s personal data without their consent, provided that this reason does not exceed any detrimental consequences on the person’s rights and freedoms. You need to be aware of your responsibilities since there may be circumstances in which permission is the most suitable legal basis.

Opt In vs Opt Out

The GDPR specifies conditions for legitimate requests for consent, but consent must also be given with a definite affirmative response. In other words, rather than pre-ticked boxes, people need a method that demands a deliberate decision to opt in. The ICO (Information Commissioner’s Office) asserts that opt-out alternatives “are effectively the same as pre-ticked boxes, which are outlawed,” even though the GDPR does not expressly forbid opt-out consent.

Examples of demands for valid consent include:

  • Signing a consent statement on a paper form
  • Clicking an opt-in button or link online
  • Selecting from equally prominent yes/no options
  • Choosing technical settings or preference dashboard settings
  • Responding to an email requesting consent
  • Answering yes to a clear oral consent request
  • Volunteering optional information for a specific purpose (such as optional fields in a form)
  • Dropping a business card into a box

The issue is that in order for a request for consent to be valid, the person must clearly take an affirmative action. Consent requests must not in any way rely on silence, passivity, default configurations, exploiting indifference or inertia, or default prejudice.

Problems with consent :  Because individuals now have more control over their data under the GDPR, relying on consent can be risky and time-consuming. For instance, you will need to obtain everyone’s approval once more if you are processing personal data with their consent and later decide to use that data for a different purpose. You must delete from your files anyone who declines or doesn’t respond.

Furthermore, people have the right to withdraw their consent at any moment, which once again requires you to delete them from your database. If you don’t do this, the relevant supervisory authority may discipline your organisation.

Additionally, you may find yourself in a catch-22 situation if a data subject withdraws their consent and you later realize you are required by law to continue processing the data. In other words, you either fail to fulfil your legal obligation to handle the data or you are compelled to violate privacy law by processing the data after consent has been withdrawn.

Everything you need to know about HIPAA

Health Insurance Portability and Accountability Act of 1996 (HIPAA) is a federal law, mainly focused on protecting sensitive patient health information from being disclosed without the patient’s consent or knowledge. The law that provides baseline privacy and security standards for medical information of US citizens and included Administrative Simplification provisions that required HHS to adopt national standards for electronic health care transactions and code sets, unique health identifiers, and security

Healthcare information regulated by HIPAA is called protected health information (PHI). PHI is any demographic information that can be used to identify a patient. PHI can include a patient’s name, address, Social Security Number, insurance ID number, medical record, full facial photograph, and others.

HIPAA compliance involves fulfilling the requirements of the HIPAA of 1996, it’s subsequent amendments, and any related legislation such as the Health Information Technology for Economic and Clinical Health (HITECH) Act.

Applicability of HIPAA

Under HIPAA regulation, there are two classes of healthcare organizations that must be HIPAA compliant. These are:-

Covered Entity– A covered entity is a health care provider, a health insurance plan or a health care clearing houses whose activity is to creates, maintains or transmits PHI. Most health care providers employed by a hospital are not covered entities. The hospital is the covered entity and responsible for implementing and enforcing HIPAA complaint policies. Examples like

Business Associate– Person or business that provides a service to or performs a certain function or activity for a covered entity when that service, function or activity involves the business associate having access to PHI maintained by the covered entity. Examples like IT Managed Services, Hosting providers, Medical Transcription Services, Billing Services etc.,

HIPAA Rules:

Since HIPAA legislation passed in 1996, Department of Health and Human Services (HHS) added multiple Rules to protect patients Privacy and Security of the patients data.

HIPAA rules that require healthcare organizations — and their business associates — to protect patient privacy and secure patient data by ensuring technical, physical, and administrative safeguards are in place and adhered to, that they comply with the HIPAA Privacy Rule in order to protect the integrity of PHI, and that – should a breach of PHI occur – they follow the procedure in the HIPAA Breach Notification Rule.

HIPAA Compliance required on the following rules.

  1. Security Rule
    – Technical Safeguards
    – Physical Safeguards
    – Administrative Safeguards
  2. Privacy Rule
  3. Breach Notification Rule
  4. Omnibus Rule
  5. Enforcement Rule

The Security Rule sets national standards for protecting the confidentiality, integrity, and availability of electronic protected health information.

The HIPAA Privacy Rule governs how ePHI can be used and disclosed. In force since 2003, the Privacy Rule applies to all healthcare organizations, the providers of health plans (including employers), healthcare clearing houses and – from 2013 – the Business Associates of covered entities.

The Privacy Rule demands that appropriate safeguards are implemented to protect the privacy of Personal Health Information. It also sets limits and conditions on the use and disclosure of that information without patient authorization. The Rule also gives patients – or their nominated representatives – rights over their health information including the right to obtain a copy of their health records – or examine them – and the ability to request corrections if necessary.

Breach Notification Rule:

The HIPAA Breach Notification Rule sets standards for the process that covered entities and business associates must follow in the event of a breach. The HIPAA Breach Notification Rule requires covered entities to notify patients when there is a breach of their ePHI. The Breach Notification Rule also requires entities to promptly notify the Department of Health and Human Services of such a breach of ePHI and issue a notice to the media if the breach affects more than five hundred patients.

Omnibus Rule:

HHS enacted the  final Omnibus Rule  in 2013 to address policy gaps in earlier HIPAA rules. Most notably, the Omnibus Rule defines the role of business associates, which were not previously subject to HIPAA rules, and outlines the criteria for Business Associate Agreements (BAAs) which must be executed between organizations sharing PHI before any information is transferred, handled, or maintained.

Enforcement Rule:

The  Enforcement Rule  empowers HHS to enforce the Privacy and Security Rules. It gives OCR the authority to investigate HIPAA complaints, conduct compliance reviews, perform education and outreach, and  levy fines  of up to $1.5 million. OCR also works with the Department of Justice to refer possible criminal violations of HIPAA.  Read more about HIPAA Rules

Steps to became HIPAA Compliant:

  1. Implementing written policies, procedures, and standards of conduct.
  2. Designating a compliance officer and compliance committee.
  3. Conducting effective training and education.
  4. Developing effective lines of communication.
  5. Conducting internal monitoring and auditing.
  6. Enforcing standards through well-publicized disciplinary guidelines.
  7. Responding promptly to detected offenses and undertaking corrective action.

Need more insights ? Get in touch with our experts for any queries on HIPAA Assessment and Compliance.

What Is HIPAA Privacy Rule?

The Health Insurance Portability and Accountability Act of 1996 (HIPAA) is a law in the United States that was created to ensure the privacy and security of health data. The Privacy Rule, also known as the Standards for Privacy of Individually Identifiable Health Information, is one of the most important parts of HIPAA. It defines how healthcare providers, health plans, health care clearinghouses  and other entities covered by HIPAA can use and disclose an individual’s protected health information (PHI). 

The act also covers health care providers that conduct certain health care transactions electronically. 

The Privacy Rule limits uses and disclosures to certain circumstances: 

–  To provide treatment, 
–  For payment, 
–  For healthcare operations, 
–  For public health activities, 
–  In specialized government functions such as military or intelligence purposes, 
–  For research purposes with consent, or 
–  If required by law. 

The Privacy Rule requires covered entities to provide individuals with notice about their privacy practices, including how they use and disclose their personal health information. It also limits certain uses and disclosures of this information without an individual’s written authorization. The key standards outlined by the HIPAA Privacy Rule cover:

– Patients’ rights to access PHI
– Health care providers’ rights to deny access to PHI,
– Contents of Use and Disclosure  HIPAA release forms
– Notices of Privacy Practices, and more. 

The Privacy Rule gives individuals rights over their protected health information, including the right to examine and obtain a copy. The Rule also gives individuals the right to request in writing that an organization restrict uses or disclosures of their protected health information.  

The regulatory standards must be documented in the organization’s HIPAA Policies and Procedures.