
@ShahidNShah
EXPLANATION OF THE MOST COMMON TYPES OF INFORMATION ASSURANCE RISKS
ADMINISTRATIVE RISKS
Risk: Lack of documentation to mitigate threats and vulnerabilities
Explanation: Not having a formal, documented program, which is always secondary to thorough risk analysis, might be the reason why you’re not able to implement effective safeguards to protect your ePHI against possible vulnerabilities and security threats. This may compromise your ePHI security in several ways:
Mitigation: Conduct an annual risk analysis and document all possible threats and vulnerabilities to your practice’s ePHI. Based on the documented risks and vulnerabilities, implement appropriate security measures specifically targeted to mitigate the vulnerabilities to an appropriate level!
Success Criteria: Documentation of possible risks and implementation of safeguards leading to reduction in security breaches.
Risk: Lack of security awareness and training.
Explanation: The security of your practice’s ePHI might be at risk if your workforce members don’t comply with the standard security protocols, either due to the lack of awareness or due to the lack of training. Several factors that may contribute to such behavior may include:
Mitigation: You can strengthen security awareness and training among your workplace members and thereby improve the security of your practice’s ePHI by taking following steps:
Success Criteria: Improved awareness and better compliance on part of the workplace members leading to strengthened security.
Risk: Lack of roles delegation.
Explanation: Your business associates or workforce members can, knowingly or unknowingly, access the confidential ePHI if your practice doesn’t clearly define, along logical lines, the roles and responsibilities allocated to each member. This is important as this will ensure that no member has too much authority and makes decisions on his own that can access critical and confidential systems and information.
Let’s explain this by a simple example. Say one of your workplace members is responsible to review the access logs. Due to your practice’s poor role delegation, the same person is also responsible for updating patient records. In this scenario, that member is essentially left to monitor his own access to ePHI, facilities and systems. This can result in unauthorized access attempts by the same member to your practice’s ePHI.
Mitigation: Some important safeguards that may help solve this issue may include:
Success Criteria: Decrease in the incidence of security breaches from within the organization.
Risk: Lack of business associate agreements when it has a contractor creating, transmitting or storing ePHI
Explanation: The safeguard of your ePHI is incomplete until enough security safeguards are provided by the service providers, as per agreement. If your service provider fails to provide enough safeguards, it may result in:
Mitigation: Before getting into a contract with your service provider, make sure that your provider gives satisfactory assurances regarding the creation, transmission, storage and handling of ePHI. Such assurances may include:
Success Criteria: Highest level of security services further strengthened by the service providers leading to improved experience and better security.
Risk: Not having a process for periodically reviewing risk analysis policies and procedures and making updates as necessary
Explanation: In something as dynamic as healthcare security, the nature of risks and threats changes with time. That’s why the efficacy of the safeguards you put to mitigate those risks declines with time. The security of your ePHI might be at risk if you fail to periodically assess the nature of risks, the validity of your policies and procedures and undermine the importance of making regular updates for improving the safeguards.
Primary Mitigation: Do a periodic risk analysis to determine the nature and severity of emerging risks to your ePHI. Keeping in mind the result of the analysis, make upgrades in your policies and procedures. Once you’re done with the paperwork, translate what you’ve learned from the risk analysis and the changes you’ve made in your policies into actually strengthening the safeguards of your ePHI.
Secondary Mitigation: Risk analysis and making changes in your policies and procedures is not a one time job. Make sure to repeat the same routine periodically – have daily, weekly, monthly, quarterly, and annual checklists to review different types of risks.
Success Criteria: Successive risk analysis reports will show that the changes made in the policies and subsequently in ePHI safeguards led to significant decrease in security breaches.
Risk: Not having a senior-level person whose job it is to develop and implement security policies and procedures or act as a security point of contact.
Explanation: Not having a senior level person who manages your security team can be jeopardizing the safety of your operations. Although security implementation and maintenance is a team effort, but having a capable person who leads that team is equally important. Moreover, the head of your security will act as a liaison between the security department and the policy makers. If that link is missing, you might not be able to influence the decisions of your higher ups when it comes to defining policies and procedures.
Primary Mitigation: Identify the security official who is responsible for heading the security team. Define her role as being an individual who actively takes part in policy making. Finally, she should be responsible for the implementation of the policies for strengthening ePHI security.
Success Criteria: Having a senior security officer who actually influences policy making, reviews documentation, runs scans, establishes a secure infrastructure, and strengthens ePHI security as a result.
Risk: Not having an emergency mode operations plan to ensure the continuation of critical business processes that must occur to protect the availability and security of ePHI immediately after a crisis situation.
Explanation: The functioning of healthcare processes, including ePHI, is always a tug of war between the security safeguards and security threats. The security can be compromised anytime, both by extrinsic or intrinsic threats, which might compromise the functioning of your entire business operations.
Having an emergency mode helps you carry out critical operations and assists you practice operation and secure the integrity of your ePHI in the event of an emergency. Emergency operation allows you to access controls, backup the data, access logging and allows encryption while other things go down. If your practice is not having an effective emergency mode, you might not be able to provide services to the end users in the event of an emergency. In addition, you not being able to carry out important business processes may compromise the security of your process and ePHI even further.
Primary Mitigation: Primary mitigation of this risk may include:
Secondary Mitigation: Test the continuity of operations during an emergency mode, on regular intervals, so that the system can be promptly shifted to the emergency mode in case of need.
Success Criteria: Your ability to readily shift to the emergency mode in cases of system collapse, run critical operations and maintain ePHI security all mark the success of emergency mode establishment and implementation.
Risk: The practice of not having policies and procedures for the creation and secure storage of an electronic copy of ePHI that would be used in the case of system breakdown or disaster.
Explanation: Like any other form of data, ePHI may be lost in case of system breakdown or disaster, if a proper backup in not kept and maintained. Backup of an ePHI is important as it allows you to create and maintain the retrievable copies of ePHI in case of emergency. The exact retrievable copies of ePHI can be established and maintained in media like physical, removable media (e.g. CDs, USBs) or virtual media (e.g. cloud storage).
Primary Mitigation: Establish and implement policies and procedures for making copies of ePHI on either physical or virtual media that can be retrieved when there is a breakdown of system.
Secondary Mitigation: Make sure that the retrievable copies of ePHI are safe and protected against unauthorized use and disclosure.
Success Criteria: Being able to retrieve ePHI from the backup sources when the main source breaks or faces a disaster.
Risk: Not having policies and procedures for the review of information system activity
Explanation: Reviewing the activity of information system enables one to identify and investigate irregular use of system, which might be due to some breach in your security protocols or maybe a violation of your security policies. Reviewing the activity of information system includes:
If you don’t have defined procedures or policies to analyze these activities, you might not be able to detect and analyze security violations, unauthorized disclosure or use of ePHI.
Mitigation: Establish a system for reviewing the records of activity of information security system. This includes reviewing incident tracking reports, audit logs, access reports and so on.
Success Criteria: Being able to detect and analyze any anomalies after reviewing information security system activity records.
Risk: A practice that doesn’t identify members of its incident response team and assure workforce members are trained and that incident response plans are tested
Explanation: An incident response consists of defining, clearly, what constitutes a security incident and a step by step approach to how to deal with the situation afterwards. Without an effective incident response and training of the workforce involved, the security of ePHI will always be a far cry. In the absence of incident response and workforce training, the security of your system will be compromised. Not to mention, it will also increase the cost, time of recovery and will exacerbate the damage done to your critical processes.
Primary Mitigation: An effective incident response plan would consist of following components:
Secondary Mitigation: Training and increasing awareness regarding incident in other workforce members too.
Success criteria: Successfully identifying which situations qualify to be labeled as an incident and successfully handling those uneventful events without compromising the security and mitigating the cost and time of recovery.
Risk: Not implementing the information system’s security protection tools to protect against malware.
Explanation: It is important that you complete regular and real time scans of your servers, workstations (including laptops and other electronic devices), and information systems so that you’re able to identify and respond to the known or suspected cases of security incidents. If you’re not implementing these protocols, the security of your ePHI and other critical business operations may get compromised.
Mitigation: Mitigation steps may include:
Success Criteria: Improved protection against malware, decrease in the incidence of malware attacks and mitigation in the compromise of the sensitive business components as the result of malware attacks.
Risk: Not regularly reviewing information system activity
Explanation: Reviewing the activity of your business operations and system activity is a periodic process that you have to do on day to day basis. If you’re not doing that then perhaps you’re overlooking some very crucial threats to your system security.
Mitigation: Establish a system for reviewing the records of activity of information security system on day to day basis. This includes reviewing incident tracking reports, audit logs, access reports and so on.
Success Criteria: Being able to detect and analyze any anomalies after reviewing information security system activity records on daily basis.
Connecting innovation decision makers to authoritative information, institutions, people and insights.
Medigy accurately delivers healthcare and technology information, news and insight from around the world.
Medigy surfaces the world's best crowdsourced health tech offerings with social interactions and peer reviews.
© 2025 Netspective Foundation, Inc. All Rights Reserved.
Built on Mar 3, 2025 at 1:39pm