One of the questions I hear most often from home health administrators, hospice agency owners and nursing homes associations considering ShieldForce is: "How long until we're actually protected?" The answer — 72 hours for core controls — consistently surprises people who have been told by enterprise security providers that deployment takes six to eight weeks. The difference is not that we cut corners. The difference is that we have deployed the same controls at hundreds of home health agencies and the process is engineered, not improvised.
The 72-hour timeline means that from the moment your contract is executed, you are 72 hours from having MFA enforced on all accounts, behavioral EDR active on enrolled devices, advanced email security filtering inbound and outbound traffic, and backup initiated for critical data. The HIPAA documentation package takes longer — 30 days — because it requires information about your specific operations that takes time to gather and verify. But the technical security posture that protects you from active threats is live within three days.
Day 1: Assessment, Access, and Architecture
The first day of every ShieldForce engagement begins with a structured discovery call with your designated ShieldForce account team. The call establishes the critical information needed to configure your environment correctly: the total user count and user role breakdown (clinical, administrative, billing), the identity platform in use (Microsoft 365 or Google Workspace), the EHR platform and whether SSO integration is available, the device fleet composition (agency-owned versus BYOD, Windows versus Mac versus mobile), the geographic distribution of your team, and any existing security tools that are in place.
Day 1 also includes the execution of the Business Associate Agreement — signed before any ShieldForce system access occurs — and the confirmation of the administrative credentials needed to begin configuration in your identity platform and email security environment. By the end of Day 1, the ShieldForce engineering team has everything needed to begin the technical deployment.
Day 2: Technical Deployment Begins
The Day 2 technical deployment follows a sequenced order that prioritises the controls with the highest immediate protection value and the lowest deployment disruption risk:
• MFA conditional access policy creation in Microsoft Entra ID or Google Identity: the policy is created and placed in audit mode first — logging which authentications would require MFA without yet enforcing it — for a two-hour observation period to confirm no legitimate services would be disrupted by immediate enforcement. Following the observation, enforcement is activated.

