01
What the product does
Basic, Mid, Premium or sector-specific names may be used, but every bundle retains a component bill of materials.
Component-based Guardian solution bundle
Bundle the controls a customer needs without hiding what is included.
ZeroShield combines Guardian Core with selected protection, assurance and managed-defence products while preserving explicit component SKUs, quantities, entitlements and responsibilities.
Australian data residency
Guardian for Australian customers is built, operated and hosted in Australia. All Guardian customer and platform data, including backups and recovery copies, is maintained and stored within Australia.
Guardian Core foundationExplicit product componentsDirect and MSP commercial modelsBilling-ready quantities
Buyer decision summary
Know what ZeroShield Security Bundles does, what the customer sees and what Damocles is responsible for before activation.
Guardian retains bundle, component product, quantity, entitlement, connector, source state, actions, evidence, service status and effective-date history.
The proposal identifies every component product, quantity, price kind, service tier, effective date, licence, connector, support and responsibility. A bundle discount or package price must still retain an auditable component allocation.
Products, quantities, allowances, connectors, supplier costs, coverage hours, service levels, effective dates, renewals and exit handling remain explicit.
02
What the customer sees
The bundle presentation does not hide the individual product status, allowance or action workflow.
03
What Damocles manages
Each underlying product retains its own support and operating boundary.
The operational problem
A bundle should make buying easier without making delivery, entitlement or billing ambiguous.
Security bundles often sound simple at sale time but create confusion when nobody can identify which users, endpoints, websites, sources, targets, service hours or responsibilities were included.
ZeroShield is a commercial packaging layer. Guardian still records the component products, quantities, effective dates, costs, service levels and billing relationship required to operate and invoice the solution correctly.
01
Start with the Core foundation
Use the shared workspace, dashboard, risk, actions, learning, baseline monitoring and reporting.
02
Add explicit products
Select protection, assurance and managed-defence products using stable product codes and measurable quantities.
03
Keep billing and entitlement auditable
Apply the correct direct or wholesale price while preserving the customer product allocation.
Product capability
A bundle structure designed to map into Guardian entitlement and billing.
Basic, Mid, Premium or sector-specific names may be used, but every bundle retains a component bill of materials.
GC
Guardian Core component
Customer workspace, dashboard, risk, All Actions, University, dark web, website monitoring and standard reporting.
MP
Managed protection components
Endpoint, patching, DNS and Svalinn products with explicit protected quantities.
AS
Assurance components
Vulnerability, Katana, external monitoring and infrastructure assessment according to scope.
MD
Managed defence components
Security Monitoring and Aegis coverage with explicit sources, capacity and service responsibilities.
EN
Entitlement mapping
Activate customer and provider access, product limits, connectors and effective dates matching the purchased components.
BI
Billing relationship
Use Guardian wholesale for external MSPs and Guardian direct for direct or Guardian-managed customers.
What the customer sees
Customers see one solution while Guardian preserves the product detail needed to operate it.
The bundle presentation does not hide the individual product status, allowance or action workflow.
OV
Solution overview
Current included products, coverage, service state, material risk and open actions.
PD
Product detail
Drill into endpoint, DNS, website, vulnerability, monitoring, learning and other selected components.
US
Usage and allowance
Users, participants, endpoints, websites, targets, sources and other measurable product quantities.
SR
Service responsibility
Customer, MSP and Damocles responsibility for each product and managed activity.
RP
Combined reporting
Current posture and improvement across the selected bundle without losing source traceability.
RN
Renewal view
Effective dates, quantities, changes and product allocation needed for commercial review.
What Damocles manages
Damocles manages the bundle design, product activation and service coordination according to the proposal.
Each underlying product retains its own support and operating boundary.
DS
Solution design
Map customer outcomes, existing tools, responsibilities, quantities and the required Guardian package.
BM
Bill of materials
Record each product, quantity, allowance, service tier, connector and effective date.
ON
Coordinated onboarding
Sequence customer, provider, product, connector, user and device onboarding across the solution.
SM
Service management
Review product health, actions, changes, usage and service responsibility across the bundle.
CM
Commercial management
Apply the approved price kind, quantity, variation and renewal without changing product entitlements silently.
SR
Solution reporting
Provide combined executive and customer reporting while retaining component product evidence.
Operating lifecycle
From customer need to explicit component subscription and entitlement.
The bundle parent helps quote and communicate the solution; component records govern delivery and billing.
01
Assess the need
Identify customer risks, existing tools, internal capability, provider role and required outcomes.
02
Choose the Core band
Select users, participants, websites and baseline allowances.
03
Add products
Add each protection, assurance and managed-defence component using stable products and quantities.
04
Set responsibilities
Define customer, MSP and Damocles operating, support, escalation and remediation duties.
05
Activate and measure
Apply entitlements, connectors, product limits, effective dates and usage records.
06
Invoice and renew
Use the approved price book and quantities while preserving the component allocation.
Common use cases
Common ZeroShield packaging models.
Each remains component based even when marketed under a simple solution name.
SB
Small-business bundle
Combine Core with selected endpoint, DNS, website and monitoring products for a defined staff estate.
ND
NDIS provider bundle
Combine provider staff protection, Participant Free, website, learning and optional managed defence.
MS
MSP wholesale bundle
Allow the MSP to buy explicit Guardian products at wholesale and set its own customer retail price.
EN
Enterprise bundle
Combine Core, Assurance, security monitoring, reporting and selected protection across a defined estate.
AP
Application-security bundle
Combine Core website monitoring, Katana, Svalinn, code review or penetration testing according to need.
MD
Managed-defence bundle
Combine Security Monitoring, Aegis, vulnerability and endpoint products with explicit source and coverage scope.
Operating model
How ZeroShield Security Bundles is onboarded, integrated, evidenced and scoped commercially.
These details remain explicit before activation, but are grouped into one operating view so buyers can review the responsibilities without working through four separate page sections.
ON
Onboarding and implementation
Bundle onboarding follows the product dependencies rather than activating everything at once. Damocles confirms the customer and provider relationship, Core package, component products, quantities, connectors, existing tools, contacts, service levels, support, effective dates, billing party and renewal. The implementation plan sequences customer workspace, identity, users, devices, sites, targets, sources, policy, agents and managed-service onboarding according to technical dependency and customer capacity. Go-live requires product-level acceptance, source health, entitlement validation, support paths, reporting and a clear register of deferred, unsupported or future components.
IN
Connector and integration model
ZeroShield remains vendor neutral because connectors sit beneath component Guardian products. The bundle references Guardian product contracts such as endpoint protection, vulnerability management or security monitoring. The selected compatible connector is recorded in the product implementation rather than replacing the public product name. A customer can retain a suitable supported technology or request a connector assessment. Changing the connector must not silently change the purchased product outcome, quantity or service responsibility. Future Guardian billing should use stable product codes, effective-dated price entries, bundle items, subscriptions, entitlements and usage records.
EV
Data, evidence and reporting
Solution reporting remains traceable to every component product and customer record. Guardian retains bundle, component product, quantity, entitlement, connector, source state, actions, evidence, service status and effective-date history. Combined reports summarise the solution while allowing authorised users to drill into the component that produced a finding or service condition. A component without data, entitlement or healthy connector remains visible rather than being hidden by the bundle name.
CM
Commercial unit and responsibilities
ZeroShield pricing is the sum or approved allocation of explicit component products. The proposal identifies every component product, quantity, price kind, service tier, effective date, licence, connector, support and responsibility. A bundle discount or package price must still retain an auditable component allocation. For external MSP relationships, Guardian invoices the MSP using Guardian wholesale prices and quantities. The MSP customer retail price is separate and must never alter the Guardian invoice. For direct and Guardian-managed customers, the applicable Guardian direct price book and contract determine the invoice.
Frequently asked questions
Questions buyers ask about ZeroShield Security Bundles.
The exact answer is confirmed in the proposal and package schedule, but these points should be understood before activation.
Q1
Is ZeroShield a separate technology?
No. It is a component-based solution bundle combining Guardian Core with selected products and services.
Q2
Can the components change?
Yes through an approved variation that records quantity, entitlement, price, responsibility and effective date.
Q3
Can an MSP set its own customer price?
Yes. The MSP retail amount is separate and does not alter the Guardian wholesale invoice.
Q4
Can existing customer tools be used?
Yes where supported connectors and operating models exist for the selected Guardian products.
Q5
Are professional services included?
Only when expressly listed as a component or engagement. Guardian can track their findings without including the work automatically.
Q6
How will this map into Guardian billing?
Through stable products, bundle items, price entries, subscriptions, entitlements, usage and invoice lines.
Scope and boundaries
A bundle name never replaces the component product and service schedule.
Products, quantities, allowances, connectors, supplier costs, coverage hours, service levels, effective dates, renewals and exit handling remain explicit.
ZeroShield pricing is not published publicly until the approved component bill of materials and price book are complete.
The bundle does not imply that every Guardian product, connector or managed service is included.
Take the next practical step
Build a solution around the customer controls and service responsibilities that are actually required.
We will define the Core band, component products, quantities, compatible connectors, commercial relationship and entitlement model.