Who can help with Netskope in Adelaide?
Subnet can. We are based in Forestville, Adelaide, and deliver Netskope work as scoped consulting engagements: reviewing an existing tenant, building a practical policy baseline, and reporting on cloud and AI use so you can decide what to allow.
How is a Netskope approach different from a VPN and a firewall?
Netskope contrasts its Private Access product with a VPN that grants access to the whole network, describing access to specific authorised applications instead. Web and cloud controls are a separate layer: Netskope describes its secure web gateway as inspecting SaaS application content and context, not only the URLs and web objects a traditional web filter sees. Whether these would replace, reduce or sit alongside your current VPN and firewall depends on your environment, so Subnet’s Netskope work starts with an assessment. Private Access design is separately scoped, and SSE on its own is not full SASE.
What is the difference between SSE and SASE, and what does Netskope SSE include?
Netskope describes Security Service Edge (SSE) as converging a secure web gateway (SWG) and cloud access security broker (CASB), with zero trust network access (ZTNA), firewall as a service, remote browser isolation and data loss prevention (DLP) alongside. SASE is the broader architecture: Netskope lists software-defined WAN (SD-WAN) among its components together with those security services. SSE is the security half; networking is the other, and the two need to be designed together. Which components suit you is a scoping decision, and Subnet’s Netskope work is delivered through separately scoped consulting and project engagements.
How does Netskope help with staff using GenAI tools such as ChatGPT?
Netskope states that its platform can identify AI use across managed and unmanaged applications, inspect prompts and responses in real time, separate personal AI accounts from corporate ones, coach users at the time of use and apply finer-grained policies than allow or block. Those are vendor capabilities that depend on licences, configuration and scope. They are not automatically part of a Subnet baseline engagement and are not a guarantee that sensitive data cannot leave. Subnet’s starting point is to understand what data users and AI tools can access, with identity, permissions and governance ahead of productivity promises.
Will Netskope show every AI tool our staff use?
Not automatically. Discovery depends on traffic being steered through operational web-security controls, so an application that is not observed does not prove nobody uses it. Discovery of local AI agents, models and MCP use has its own requirements: Netskope’s current documentation lists Windows and macOS endpoints only, with Netskope Client 138 or later for supported discovery, and some capabilities need newer versions. MCP traffic visibility requires the relevant Agentic Broker capability. Coverage, DLP, AI Guardrails and reporting vary with products, licences and configuration, so validate against current documentation and a representative pilot.
We already have a Netskope tenant. What would a baseline review cover?
For an existing licensed tenant, Subnet can scope an effort-bounded review and agreed policy changes covering tenant settings, traffic steering and client settings, SSL inspection, web and DNS security, inline CASB and threat-protection policies, exceptions and policy ordering. A pilot and handover summary help validate the baseline and record decisions and next steps. Advanced controls depend on entitlement, feasibility and separately agreed scope. It is an example of scope, not a fixed package.
What does Subnet do in a Netskope engagement, and what stays with us?
Subnet’s Netskope work is scoped as consulting or a project, separate from its managed-security service. It can cover assessment of the existing environment, baseline configuration, representative pilot testing and handover for agreed web and cloud controls. Early in scoping you and Subnet agree the traffic and users in scope, the controls to configure, the evidence the pilot should produce, and who will own licensing, implementation and ongoing operation. The example baseline does not include full endpoint rollout, ongoing tuning, full DLP or data classification, Private Access design, user training or communications, or SD-WAN changes; these are agreed separately where needed.
Who owns Netskope licensing in an engagement?
Licensing and procurement changes are agreed separately from the consulting engagement, and early scoping settles who will own licensing, implementation and ongoing operation. If you already have a licensed Netskope tenant, Subnet can scope a review of how it is configured. Which advanced controls are available depends on your entitlement, the feasibility of the change and separately agreed scope.
What will staff notice during a Netskope rollout?
An engagement starts by identifying the traffic and users in scope, then uses a representative pilot before wider change. Broader endpoint deployment, user training and communications are not part of Subnet’s example baseline and are agreed separately. Netskope documents several client deployment options for administrators, including mobile device management (MDM) tools. What staff notice depends on the policies agreed, for example alerts, coaching messages or blocked activity; coaching explains a policy at the moment of use and is not a substitute for staff training. Subnet does not state performance or downtime outcomes in advance; the pilot is where impact is checked.
Does Netskope data loss prevention classify our data for us?
DLP supports controls for sensitive information across supported channels. Classification, policy design and governance require their own decisions and scope, and full DLP or data classification is not part of Subnet’s example baseline engagement. Agree what counts as sensitive, who owns the policy and how exceptions are handled before relying on it.