Working with a managed security provider does not end when the contract is signed; the real value begins in the days that follow. The 113SEC onboarding process delivers a controlled start in 5-10 business days, from discovery and inventory to monitoring and a first risk report.
What onboarding actually means
Onboarding is the controlled way a new client is brought into a managed security service. The goal is not simply to install a few applications. It is to understand the client's infrastructure, make every asset visible, open response channels, stand up monitoring and complete a first security assessment.
In other words, onboarding is the stage where a business gets a clear answer to the question: "Are we now being monitored and managed?" The process starts once the agreement is signed, takes 5-10 business days on average, and ends with systems under monitoring, remote access prepared and a first risk report delivered.
Why it takes 5-10 business days
The word "setup" is sometimes understood as nothing more than installing a couple of programs. A secure start, however, requires more: the infrastructure must first be understood correctly, then documented, and only then can monitoring and security components be brought online.
The timeframe depends on the number of devices, the location structure, the server count, the state of remote access and the quality of any existing documentation. A small office moves quickly, while a business with multiple sites, several servers, a VLAN layout or a complex permission model needs more detailed work. In short, 5-10 business days means a start that is fast but never rushed.
The 113SEC onboarding flow
The process follows a sequence that makes the infrastructure visible step by step:
- Agreement and kickoff: The contract is confirmed and the client's points of contact, communication channels and technical owners are clarified.
- Discovery meeting: A roughly 45-minute session covers the infrastructure, current problems, critical systems, locations, user count and priority needs.
- On-site or remote access: The infrastructure is reached on-site or remotely for a network scan, device discovery and an initial technical review.
- Documentation in Hudu: Computers, servers, network devices, printers, users, IP details and critical notes are recorded in Hudu, becoming the core data source for future support, monitoring and risk analysis.
- Remote access setup: TeamViewer is deployed to the relevant devices through a corporate structure, so the team can respond securely whenever an alert or support need arises.
- Zabbix + Wazuh deployment: Zabbix enables infrastructure and performance monitoring while Wazuh covers security events and log monitoring; connections are verified after the agents are installed.
- Risk analysis: Risk analysis is not left to the end. It runs in parallel once remote access begins, covering user permissions, network security, endpoint posture, backups, licensing, physical security and data privacy.
- First risk report and service activation: Once installations are complete, the first assessment is presented, the service goes live and the business enters the scope of support, monitoring, alert management and reporting.
You can explore the monitoring and security technologies behind this flow on our technology page.
Why discovery and inventory matter so much
To manage an infrastructure you first have to know what it contains. How many computers are there? Which servers are critical? Which devices use static IPs? Are there unidentified devices on the network? Are any machines running outdated operating systems? Which users hold administrator rights?
You cannot protect an asset you cannot see. That is why one of the most important outputs of onboarding is a clear inventory.
The inventory evaluates computers, servers, printers, network devices, NAS/storage units, IP phones, cameras and IoT devices, along with any unlicensed or unidentified assets, each on its own.
Remote access must stay controlled
Setting up remote access is critical for later support and alert response, but it must never run through uncontrolled or personal accounts. TeamViewer Host installations should sit under a corporate license, be assigned to the correct account and be linked to Hudu records. This makes it clear how each device is reached, standardizes response and spares the client from juggling separate access accounts.
Onboarding is not complete without monitoring
Bringing a client on board is not finished by producing a device list; the real goal is making systems observable around the clock. Zabbix watches server, network, service and performance status, while Wazuh provides visibility into security events, logs and anomalous behavior.
Installing the agent is not enough on its own. The host must appear in Zabbix, the agent must be active in Wazuh, recent metrics must be flowing and the Hudu records must be updated. Without this verification, the process is not considered sound.
Why the first risk report is valuable
One of the strongest outputs of onboarding is the first risk report, which captures the business's current security posture as a baseline. It covers network security, endpoint security, user management, backups, licensing, physical security and data privacy. Findings are prioritized into critical, high, medium and low.
This way the client gains more than a "systems are installed" confirmation; it answers "what are our current risks and what should we fix first?" The result is a plain summary for management and an actionable plan for the technical team. That prioritization logic sits at the heart of our approach.
What the client should prepare
The process is largely driven by 113SEC. Even so, having a few details ready on the client side helps it move faster:
- Technical contact and decision-maker details
- A list of critical systems, servers and locations
- The current network layout or any older topology documents
- The backup method in use and the location of critical data
- Firewall, VPN, domain or cloud account details, where applicable
- Priority issues and any past security incidents
The process can move forward even if this information is incomplete, but the more that is ready, the faster and healthier the onboarding will be.
What you have at the end of onboarding
By the end of the process you hold more than a setup checklist; you have the foundation of a manageable IT and security structure:
- A device and system inventory
- Organized client documentation in Hudu
- A remote access setup
- Zabbix + Wazuh monitoring
- A user and permission review
- A first risk report
- An operations structure ready for support and alert response
Conclusion: a good start is the foundation of secure operations
The initial setup period determines the quality of every operation that follows. A missing inventory, uncontrolled access, an unverified agent installation or a skipped risk analysis can turn into far bigger problems later. Discovery, inventory, Hudu records, TeamViewer, Zabbix, Wazuh and the risk report work together to deliver a secure, controlled start.
Completed within 5-10 business days, this process lets a business begin its security operations not with uncertainty, but with visibility, documentation and an action plan. To plan your transition, feel free to get in touch with us.