Access to BloomAPI systems and application is limited for all users, including but not limited to workforce members, volunteers, business associates, contracted providers, consultants, and any other entity, is allowable only on a minimum necessary basis. All users are responsible for reporting an incident of unauthorized user or access of the organization's information systems. These safeguards have been established to address the HIPAA Security regulations including the following:
- 01.d - User Password Management
- 01.f - Password Use
- 01.r - Password Management System
- 01.a - Access Control Policy
- 01.b - User Registration
- 01.h - Clear Desk and Clear Screen Policy
- 01.j - User Authentication for External Connections
- 01.q - User Identification and Authentication
- 01.v - Information Access Restriction
- 02.i - Removal of Access Rights
- 06.e - Prevention of Misuse of Information Assets
- 164.308a4iiC Access Establishment and Modification
- 164.308a3iiB Workforce Clearance Procedures
- 164.308a4iiB Access Authorization
- 164.312d Person or Entity Authentication
- 164.312a2i Unique User Identification
- 164.308a5iiD Password Management
- 164.312a2iii Automatic Logoff
- 164.310b Workstation Use
- 164.310c Workstation Security
- 164.308a3iiC Termination Procedures
- Requests for access to BloomAPI Platform systems and applications is made formally to the CTO, Privacy Officer, or Security Officer.
- Access is not granted until receipt, review, and approval by the BloomAPI Security Officer;
- The request for access is retained for future reference.
- All access to BloomAPI systems and services are reviewed and updated on an annual basis to assure proper authorizations are in place commiserate with job functions.
- Any BloomAPI workforce member can request change of access by emailing the Security Officer.
- Access to systems is controlled using centralized user management and authentication. All authentication requests utilize two-factor authentication where supported.
- Temporary accounts are not used unless absolutely necessary for business purposes.
- In the case of non-personal information, such as generic educational content, identification and authentication may not be required.
- Privileged users must first access systems using standard, unique user accounts before switching to privileged users and performing privileged tasks.
- All application to application communication using service accounts is restricted and not permitted unless absolutely needed. Automated tools are used to limit account access across applications and systems.
- Generic accounts are not allowed on BloomAPI systems.
- In cases of increased risk or known attempted unauthorized access, immediate steps are taken by the Security and Privacy Officer to limit access and reduce risk of unauthorized access.
- Direct system to system, system to application, and application to application authentication and authorization are limited and controlled to restrict access.
- The level of security assigned to a user to the organization's information systems is based on the minimum necessary amount of data access required to carry out legitimate job responsibilities assigned to a user's job classification and/or to a user needing access to carry out treatment, payment, or healthcare operations.
- All access requests are treated on a "least-access principle".
- BloomAPI maintains a minimum necessary approach to access to Customer data. As such, BloomAPI, including all workforce members, does not readily have access to any ePHI.
- Role based access categories for each BloomAPI system and application are pre-approved by the Security Officer or CTO.
- BloomAPI utilizes hardware and software firewalls to segment data, prevent unauthorized access, and monitor traffic for denial of service attacks.
- Each workforce member has and uses a unique user ID and password that identifies him/her as the user of the information system.
- Access to the BloomAPI systems and applications is controlled by requiring unique User Login ID's and passwords for each individual.
- Passwords requirements mandate strong password controls (see below).
- Passwords are not displayed at any time and are not transmitted or stored in plain text.
- Default accounts on all production systems, including root, are disabled.
- Shared accounts are not allowed within BloomAPI systems or networks.
- Users are required to make information systems inaccessible by any other individual when unattended by the users (ex. by using a password protected screen saver or logging off the system).
- Information systems automatically log users off the systems after several minutes of inactivity.
- Workstations may not be used to engage in any activity that is illegal or is in violation of organization's policies.
- Access may not be used for transmitting, retrieving, or storage of any communications of a discriminatory or harassing nature or materials that are obscene or "X-rated". Harassment of any kind is prohibited. No messages with derogatory or inflammatory remarks about an individual's race, age, disability, religion, national origin, physical attributes, sexual preference, or health condition shall be transmitted or maintained. No abusive, hostile, profane, or offensive language is to be transmitted through organization's system.
- Information systems/applications also may not be used for any other purpose that is illegal, unethical, or against company policies or contrary to organization's best interests. Messages containing information related to a lawsuit or investigation may not be sent without prior approval.
- Solicitation of non-company business, or any use of organization's information systems/applications for personal gain is prohibited.
- Transmitted messages may not contain material that criticizes organization, its providers, its employees, or others.
- Users may not misrepresent, obscure, suppress, or replace another user's identity in transmitted or stored messages.
- BloomAPI production systems are not accessible directly over wireless channels.
- The Human Resources Department (or other designated department), users, and their supervisors are required to notify the Security Officer upon completion and/or termination of access needs and facilitating completion of the "Termination Checklist".
- The Human Resources Department, users, and supervisors are required to notify the IT Help Desk to terminate a user's access rights if there is evidence or reason to believe the following (these incidents are also reported on an incident report and is filed with the Privacy Officer):
- The user has been using their access rights inappropriately;
- A user's password has been compromised (a new password may be provided to the user if the user is not identified as the individual compromising the original password);
- An unauthorized individual is utilizing a user's User Login ID and password (a new password may be provided to the user if the user is not identified as providing the unauthorized individual with the User Login ID and password).
- The Security Officer will terminate users' access rights immediately upon notification.
- The Security Officer audits and may terminate access of users that have not logged into organization's information systems/applications for an extended period of time.
BloomAPI does not use paper records for any sensitive information. Use of paper for recording and storing sensitive data is against BloomAPI policies.
- User IDs and passwords are used to control access to BloomAPI systems and may not be disclosed to anyone for any reason.
- Users may not allow anyone, for any reason, to have access to any information system using another user's unique user ID and password.
- Passwords are inactivated immediately upon an employee's termination (refer to the termination procedures in this policy).
- All default system, application, and Partner passwords are changed before deployment to production.
- All passwords used in configuration scripts are secured and encrypted.
- If a user believes their user ID has been compromised, they are required to immediately report the incident to the Security Office.