TABLE OF CONTENTS
- 1. Purpose
- 2. Scope
- 3. Policy Statement
- 4. Criteria for Temporary Suspension of Client Access
- 5. Approval Process for Client Access Suspension
- 6. Emergency Suspension Process
- 7. Client Notification
- 8. Client Requirements for Restoration of Access
- 9. Approval Process for Restoration of Access
- 10. Documentation and Audit Requirements
- 12. Policy Compliance and Review
1. Purpose
This policy defines Streets Heaver Healthcare Computing process for responding to client security incidents, including the circumstances under which client access to Compucare, infrastructure, and related products and services may be temporarily suspended to protect the confidentiality, integrity, and availability of services, systems, and data.
The policy also defines the approval process and roles responsible for suspending and restoring client access.
2. Scope
This policy applies to:
- All client access to Compucare, infrastructure, and related products and services.
- All employees, contractors, and third parties
- All security incidents affecting client accounts, client data, Compucare, infrastructure, products, or services
2.1 Definition of Access Suspension
For the purposes of this policy, temporary suspension of client access may include one or more of the following actions, depending on the nature and severity of the security incident:
- Blocking or disabling access for a specific affected user account.
- Suspending a compromised client account.
- Disabling access to specific products, services, or functionality.
- Restricting access from identified IP addresses, devices, or locations.
- Taking a client database or client environment offline where applicable to contain, investigate, or remediate a security incident.
- Any other temporary access control measure deemed necessary to protect Compucare, infrastructure, related products and services, client data, or other clients.
Such measures shall remain in place only for as long as reasonably necessary to contain and remediate the identified risk and shall be reviewed as part of the restoration process.
3. Policy Statement
Streets Heaver shall take appropriate action to detect, contain, investigate, and remediate security incidents that may impact clients, services, systems, infrastructure, or data.
Where necessary to mitigate risk, prevent further compromise, or protect Compucare and services, client access may be temporarily suspended. Temporary suspension may include the suspension of individual user accounts, the restriction of access to specific services, or taking a client database or environment offline where applicable.
Any suspension or restoration of access must follow the approval and documentation requirements defined in this policy.
4. Criteria for Temporary Suspension of Client Access
Client access may be temporarily suspended when one or more of the following conditions exist:
4.1 Account or Security Compromise
- Confirmed or suspected compromise of a client account.
- Evidence of stolen, exposed, or misused credentials.
- Unauthorized access attempts using a client account.
- Evidence that a client account is being used maliciously.
4.2 Risk to Compucare and Related products
- Client activity is causing or is likely to cause service degradation or operational instability.
- Client activity poses a significant threat to the security, availability, confidentiality, or integrity of Compucare, infrastructure, and related products and services.
- Malware, ransomware, or other malicious activity has been detected originating from or associated with a client account or connected client systems.
4.3 Client Security Incident
- A client system connected to or interacting with Compucare services has been breached.
- A breach on the client side presents a risk to Compucare systems, services, or other clients.
- A client is unable to demonstrate that a known compromise has been appropriately contained.
4.4 Legal or Regulatory Requirements
- A legal, regulatory, contractual, or governmental requirement necessitates suspension of access.
- Continued access would result in non-compliance with security, legal, or contractual obligations.
4.5 Incident Containment
- Temporary suspension is necessary to contain an active security incident and prevent further impact while investigation and remediation activities are performed.
5. Approval Process for Client Access Suspension
5.1 Standard Suspension Approval
The decision to suspend client access must be approved by one of the following:
- A member of the Executive Team;
OR
- A Lead / Senior Engineer within the relevant Product Team and
- A member of the Platform Engineering Team.
Approvals must be recorded within the incident record before suspension is performed whenever reasonably practicable.
5.2 Documentation Requirements
The following information must be documented:
- Client name.
- Reason for suspension.
- Systems, products, or services affected.
- Risk assessment.
- Approval records.
- Date and time of suspension.
- Personnel performing the suspension.
- Actions Performed
6. Emergency Suspension Process
In circumstances where immediate action is required to protect Streets Heaver, clients, or services from imminent risk, client access may be suspended before the standard approval process can be completed.
Emergency suspension may be approved by:
- Platform Engineering Team Lead; or
- In their absence, a Senior Engineer within the Platform Engineering Team.
Following an emergency suspension:
- The incident must be formally documented as soon as possible.
- Relevant stakeholders must be informed.
- The incident shall undergo management review.
- Standard approvals shall be retrospectively recorded where appropriate.
7. Client Notification
Unless prohibited by legal, regulatory, investigative, or security considerations, affected clients shall be notified of:
- The access suspension.
- The reason for the suspension.
- Required remediation actions.
- Steps required for access restoration.
- Any relevant timelines or updates.
8. Client Requirements for Restoration of Access
Where a client account or client-managed system has been compromised, Streets Heaver may require written confirmation from the client that remediation has been completed before access is restored.
The client must provide written confirmation that applicable remediation actions have been completed, including:
8.1 Account Compromise
Where a client account has been compromised:
- All affected account passwords have been reset.
- Any compromised credentials have been revoked.
- Multi-factor authentication has been enabled or revalidated where applicable.
- Unauthorized access has been terminated.
8.2 Client System Compromise
Where a client device or system has been compromised due to malware, phishing, malicious downloads, or other security incidents:
- The affected system has been isolated and contained.
- Any malicious files have been removed.
- Any malicious links or phishing-related activity has been investigated.
- If a computer it is wiped to remove all malicious files.
- The affected system has been rebuilt, restored, or reset as appropriate.
- Necessary security updates and remediation measures have been applied.
- The client has verified that the threat is no longer active within the affected environment.
Streets Heaver reserves the right to request additional evidence or assurance where necessary to protect its systems, infrastructure, products, or services.
9. Approval Process for Restoration of Access
Access restoration shall only occur when:
- The incident has been investigated.
- Identified risks have been mitigated to an acceptable level.
- Required remediation activities have been completed.
- Any required client confirmations have been received.
- The threat has been contained and is no longer considered active
9.1 Restoration Approval
Restoration of client access must be approved by:
Either
- A member of the Executive Team;
Or
- A Lead Engineer within the relevant Product Team or a Senior Engineer within the relevant Product Team and
- A member of the Platform Engineering Team.
The approval decision must be documented within the incident record.
10. Documentation and Audit Requirements
All suspension and restoration activities must be recorded, including:
- Incident details.
- Investigation records.
- Risk assessments.
- Client communications.
- Approval records.
- Suspension timestamps.
- Restoration timestamps.
- Corrective actions taken.
- Post-incident review findings.
Records shall be retained in accordance with Streets Heaver's information security and record retention requirements.
11. Policy Compliance and Review
This policy shall be reviewed:
- Annually.
- Following any major security incident.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article