A separate Kali Linux environment for scoped security assessments, training and defensive research. Keep your tools in Switzerland and your testing within systems you own or have permission to assess.
A compact Kali setup for command-line tools, introductory labs and focused authorized testing. Its base allocation is 2 vCPUs, 2 GB of DDR4 memory and 30 GB of SSD storage.
A Kali Linux workspace for authorized assessment tools and security study. It combines 5 Xeon 5600 vCPUs, 2 GB of DDR4 memory and a 45 GB SSD with a 3 TB traffic allowance.
Eight vCPUs and 4 GB of DDR4 memory provide room for a wider collection of Kali tools and research tasks. The configuration includes a 60 GB SSD and 5 TB of traffic.
A larger Kali environment for authorized work that needs more processes and working files: 12 vCPUs, 8 GB of DDR4 memory, a 100 GB SSD and a 10 TB traffic allowance.
Compare the listed specifications and base prices. Final availability, delivery and applicable tax are confirmed on your quote. Illustrations are conceptual.
Understand what makes this service family useful.
Use a Kali environment away from your everyday computer. Organise project tools, notes and approved test data inside a dedicated KVM system.
Select the GUI and VNC options when a desktop interface fits your work. Keep their access limited to the people who need it.
Choose CPU, RAM and SSD capacity for the tools and datasets involved. Additional resources let you adapt the workspace to a defined project.
Optional backup retention can support ongoing work. Consider what sensitive assessment material a backup contains before selecting how long to keep it.
Prepare and perform tests against an agreed set of systems with a documented scope and permission from the owner.
Work with your own deliberately vulnerable labs and exercises without mixing them into your daily workspace.
Evaluate approved security utilities, reproduce findings in a lab and prepare clear evidence for remediation.
List the authorised targets, permitted techniques, time window and people who can approve changes to the assessment. Sentinel Kali provides the environment; it does not grant permission to access a third-party system. Keep the workspace aligned with the agreed assessment and avoid unrelated traffic.
Assessment notes, logs and captured evidence may contain sensitive information. Use separate project directories, limit access and establish a retention period before work begins. If you select automatic backups, include those copies in the same data-handling plan rather than treating them as harmless duplicates.
A command-line environment keeps the setup focused for scripted tasks. A graphical session can suit tools that require a desktop, but it also needs memory and careful remote-access controls. Review the GUI, VNC, resource and network options together when configuring the workspace.
Kali supplies a security-focused starting point, but a named distribution does not establish every package or version in a delivered image. Confirm the installed toolset and root credentials, plan SSH access, and review the separate GUI and VNC options if needed. The base plans list Layer 3–4 protection; later upgrades, console recovery and custom-image requests require operator confirmation.
Available choices depend on the selected configuration. See included selections and option prices in the configurator.
Specific answers for this service family.
Only with explicit authorisation and an agreed scope. Purchasing a security environment does not authorise scanning, exploitation or access to third-party systems.
The configurator includes GUI and VNC choices. Review both selections and allow enough memory for the desktop and tools you plan to run.
No. Sentinel is intended for authorised assessments, education and defensive research. Fraud, harmful attacks and unauthorised access are outside the service's intended use.
Only when it fits the project's handling and retention rules. Evidence may contain confidential client data; include backup copies in your access and deletion plan.
The starting security distribution differs. Compare the tools and workflow you need, then review the actual resources and available options for the selected family.
Confirm the delivered image, package versions and tools required for the assessment. No fixed tool count or complete preinstalled suite is promised by the current catalogue.
Plan SSH for command-line work and confirm root credentials at delivery. GUI and VNC are separate configuration choices. Secure every entry point before installing or using assessment tools.
Layer 3–4 protection is in the base plan. CPU, memory, disk and network additions are configurable, while a change to an existing workstation requires a confirmed procedure and availability.
It can form part of an authorised analysis workflow. Preserve evidence separately, verify tool suitability and avoid altering original material; the server alone does not establish a forensic chain of custody.
Choose your resources. Keep control of your identity.