Support for organizations already running ASPIS.
Technical assistance for existing customers: configuration and policy questions, deployment problems, integration behavior, and anything that needs an ASPIS engineer rather than a sales conversation.
If something is happening right now, say so in the first line.
Email support@aspiscyber.com and lead with the word incident, the organization name, and what you are seeing. Include the detail below if you have it, but do not wait to gather all of it — send what you know and follow up.
If you administer the tenant, ManageiT shows current alerts, affected devices and recent policy and administrative changes, which is usually the fastest way to establish scope while the conversation starts.
How to reach support
Any of these routes reach the same team. Email is the most direct if you already know what you need; the form is there if you would rather describe the situation in structured fields.
Email support
Direct to the support address ASPIS publishes for existing customers.
support@aspiscyber.comSupport inquiry form
The contact form with Support already selected, so the inquiry is routed rather than triaged.
Open the formAdministrator access
ManageiT, the ASPIS administration portal, for tenant administrators.
ManageiT Log In ↗What to include
None of this is required to open a conversation. It is simply what tends to make the first reply useful rather than a request for more information.
Organization and tenant
The organization name and, if you know it, the tenant the affected users sit in. ManageiT shows this on the dashboard header.
Product and edition
Which ASPIS product is involved — ShieldiT Enterprise, FSX, Executive, Defense, ManageiT or SentinelIQ — and the edition, where you know it.
Scope
One user, one group, one device platform, or the whole estate. Whether it started after a policy change, an OS update or a new deployment.
What you observe
What happens, what you expected instead, and when it began. Exact on-screen text is more useful than a paraphrase.
Devices and platforms
Operating system and version on the affected devices, and whether they are corporate-managed or BYOD.
What you have already tried
Steps already taken, and anything that changed the behavior. It saves a round trip.
Before you raise it
Configuration, deployment and architecture questions are often answered by the published material or visible in the console.
ManageiT
Tenant and user administration, security policy, alerts, audit logs and integration status. Where an administrator can see current state before raising anything.
Open ManageiT ↗Document library
Product white papers and use-case documents covering architecture, deployment and configuration.
Browse documentsPlatform architecture
How the products fit together, what runs where, and which controls apply at which layer.
Platform architectureReporting a security vulnerability
A suspected vulnerability in an ASPIS product is a different route from a support request, and should go through responsible disclosure rather than the support address.
Responsible disclosureNot an ASPIS customer yet
Evaluations, pricing, architecture reviews and demonstrations are handled by the sales and specialist teams, not by support.
Contact ASPISPartners
MSPs, MSSPs, carriers, resellers and integrators supporting their own customers on ASPIS have a separate route.
Partner program