We are so excited to be kicking off onboarding with you! The below document outlines in 4 clear phases the activities required to get you fully up and running with Zip!
Once we have a signed contract in place, you will be introduced to your Customer Success POC who will kick of on-boarding activities, starting with alignment on details and timelines for your launch.
Our Sales and Customer Success team work very closely together, so any requirements (particularly tight timelines for instance!) discussed during Sales will have be communicated.
Phase 1: Pre-Onboarding Information
Collecting this information will allow us to get a full understanding of your organization, and ensure that provisioning is done in line with your organization’s needs.
Device Count + Mix
Number of devices, and device types | |
IdP: What IdP are you be using? | |
Who has admin access to your IdP? | |
Email Provider | |
What MDM will you be using? [Do you currently have any MDM set up?] | |
Will Zip be providing CrowdStrike and MDR for you? | |
Do you currently have any security tools/providers in place that will require a migration? | |
Windows state of things: Microsoft admin? License reseller? | |
What Compliance Framework(s) are you target? | |
User on the Console + CrowdStrike? |
Phase 2: Setting Up the Zip Console
Once we have a clear understanding of your implementation scope, the Zip team will get right to work provisioning, and integrating your security tools and the Zip console. This phase is largely led by the Zip team, but will require some actions to be completed by the client, as outlined below..
This phase is fully managed by Zip, and any asks or actions will be communicated via email.
Key Activities
Zip Owned Activities:
Provision Zip Console
Provision Jamf
Provision Intune
Provision CrowdStrike
Provision MDR Services
Client Owned Activity:
Permission Granting:
Microsoft Temporary Admin Access [Sent by Zip, for approval]
Microsoft License Reseller Approval [Sent by Zip, for approval]
Identity Provider Onboarding:
Accept Invites to: Zip Console + CrowdStrike [Sent by Zip]
Phase 3: Configuring Your Zip Console
Once we have completed the provisioning and integration of all tools, we are ready to get the Zip Console fully configured and ready for device enrollment. This mainly involves configuring security controls and compliance frameworks so devices enrolling are immediately compliant and protected.
Key Activities
Enable & Auto-Enforce Controls
Follow the below instructions to turn on the relevant security controls for your organization.
Set up Compliance Frameworks — this allows for 1-click enablement of auto-enforced controls. If you don’t have a specific Compliance Framework you are working towards, we recommend SOC2 Framework as a great starting point!
Review Accounts and Exclude
To help with clear and accurate reporting Zip offers the functionality to tidy up and exclude any accounts or devices you do not need to be in the scope of monitoring. This could include: contractor devices, external/guest accounts,
Set Up Notifications
Zip integrates with Slack and Email to bring notifications from the Zip Console directly to your day-to-day workflows. Setting this up ensures you’re notified when something requires your attention, and have the peace of mind - that when things are quiet, everything is running smoothly.
Phase 4: Device Enrollment
By the time we reach this phase we are ready to enroll devices! You will receive an email notification from your Onboarding Lead, confirming 🟢 Device Enrollment Green Light 🟢
Follow the below steps to proceed with Device Enrollment, testing and roll out:
Key Activities
Test the Device Enrollment flow with at least 1 Mac and 1 Windows Device — we recommend using your own device to test, or a user’s who you can walk through the flow live with to ensure it runs smoothly
Device Enrollment Rollout — rollout device enrollment instructions to your employees via the Tasks tab in your Zip console
Track Device Enrollment Progress, and ensure your compliance get’s to 100% — send chasers via the Tasks tab in your Zip console
If required, Exclude Devices from Enrollment — e.g. if you have contractors on personal devices you don’t require to be enrolled, you can mark their device as not required for enrollment
If you run into any issues, please use the below troubleshooting docs to help resolve the issues:
Phase 5: Onboarding Complete!
The Zip Onboarding Team will monitoring your progress and be on hand to support with any questions or troubleshooting issues. You can reach out to info@zipsecinc.cc and a member of our team will be happy to help!
The objective of onboarding is to reach 100% Device Enrollment, and have relevant Security Controls enabled and auto-enforced.