Skip to content

Technology

Netskope

Subnet helps South Australian organisations use Netskope to see and control how staff use the web, cloud applications and AI tools, wherever they are working.

Netskope logo

Cloud-delivered

security that follows the user, not the office

Web, cloud, AI and private apps

under one set of policies

Project-based

scoped consulting engagements with clear outcomes

WHAT NETSKOPE OFFERS

Visibility and control for web, cloud and AI use

Netskope is a cloud security platform. These are the parts of the range Subnet works with most.

Web and cloud

Secure web gateway and cloud app security

Netskope inspects web and cloud application traffic from each device, applying the same policy in the office, at home or on the road.

What it solves

  • Protection that stops at the office firewall
  • No view of which cloud applications are in use
  • Risky sites reachable from remote devices

How Subnet works with it

We start in monitor mode, review what is found with you, then apply policy in stages.

AI

AI use visibility

Netskope can show which supported AI services staff are using and what kind of information is going into them.

What it solves

  • Staff using AI tools nobody approved
  • Company data pasted into public chatbots
  • No evidence to base an AI policy on

How Subnet works with it

We report on current use, help you decide what to allow and set coaching or blocking rules to match.

Private access

Zero trust access to internal applications

Netskope Private Access connects people to specific internal applications after checking identity and device, without placing them on the whole network.

What it solves

  • VPNs that expose more than needed
  • Contractors with broad network access
  • Slow or unreliable remote connections

How Subnet works with it

We map who needs which application and move groups across from the VPN in stages.

Data

Data protection

Data loss prevention policies recognise sensitive information and control where it can be uploaded, shared or pasted.

What it solves

  • Sensitive files uploaded to personal storage
  • Different rules in different tools
  • Blocking that gets in the way of work

How Subnet works with it

We agree a small number of clear rules and tune them against real activity before enforcing.

WORK WITH SUBNET

How Subnet works with Netskope

1. Assess

We confirm what you need to see or control, and what you already own.

2. Design

Policies, pilot group and success measures are agreed.

3. Deploy

The client is rolled out in stages, in monitor mode first.

4. Hand over

Policies are documented and handed to your team, or scoped for further consulting.

5. Review

Findings are reviewed with you and the next step agreed.

SEPARATELY SCOPED CONSULTING

A PROJECT ENGAGEMENT. NOT A MANAGED-SERVICE INCLUSION.

Subnet’s Netskope work is delivered through separately scoped consulting and project engagements. It can cover assessment of the existing environment, baseline configuration, representative pilot testing and handover for agreed web and cloud security controls.

The engagement should identify the traffic and users in scope, the controls to be configured and the evidence the pilot should produce. Licensing, procurement changes and broader endpoint deployment are agreed separately. Netskope is not a component of Subnet’s managed-security service.

WORK WITH SUBNET

Turn an existing Netskope investment into a practical policy baseline

For an existing licensed tenant, Subnet can scope an effort-bounded review and agreed policy changes: 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.

This example does not include full endpoint rollout, ongoing tuning, a full CASB discovery or application-governance programme, full DLP or data classification, Private Access design, user training or communications, or SD-WAN changes. Advanced controls depend on entitlement, feasibility and separately agreed scope. It is not a fixed package or evidence of a completed customer deployment.

AI SECURITY

UNDERSTAND AI USE BEFORE DECIDING WHAT TO ALLOW.

Netskope can help reveal use of supported AI services, including unsanctioned tools and personal versus corporate instances where supported. With the relevant products and configuration, organisations can review activity, apply contextual policies and guide users towards approved tools.

Controls can include alerts, coaching and blocking. Data inspection and AI-specific guardrails require the appropriate licences and scope. These are vendor capabilities to assess, not features automatically included in a Subnet baseline engagement.

01

Discover what is visible

AI application discovery relies on operational web-security controls and traffic steered through them. An application that is not observed is not evidence that nobody uses it.

02

Understand the context

Where the application supports it, distinguish the user, activity and personal or corporate instance before choosing a policy.

03

Guide the next action

Contextual coaching can explain a policy at the moment of use and direct people towards approved services. It is a policy interaction, not a substitute for staff training.

04

Report with clear boundaries

Separate observed activity, inspected traffic, policy actions and blocked activity. Agree the reporting audience and decisions the evidence should support.

COVERAGE AND DEPENDENCIES

VISIBILITY IS DESIGNED, NOT ASSUMED.

Local AI-agent, model and MCP discovery has client and operating-system requirements. Current vendor documentation specifies Windows or macOS with Netskope Client 138 or later for supported discovery; some capabilities have additional version requirements. MCP traffic visibility requires the relevant Agentic Broker capability.

Coverage, application support, DLP, AI Guardrails and reporting depend on the products, licences, deployment and configuration. Validate the current documentation and a representative pilot rather than assume universal discovery or protection.

Netskope AI Command Center documentation Client AI discovery requirements

YOUR QUESTIONS

A LITTLE MORE CLARITY.

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.

NEXT STEPS

TURN VISIBILITY INTO AN AGREED PLAN.

Start with the question you need answered: which AI services are in use, where sensitive information may move, or how remote users should reach applications. We can scope the baseline, pilot, responsibilities and any additional licensed capabilities around that need.

BEFORE WE TALK

A useful starting point.

You do not need a finished technical brief. Start with the outcome, what you know today and the questions you need answered.

  • What capability are you looking for?
  • How would it work with your current environment?
  • Who will own licensing, implementation and ongoing operation?
Discuss these priorities

LET’S TALK

WHAT WOULD YOU LIKE TO DO NEXT?

Tell us about your organisation and what you need. Start a conversation, discuss a project or request a meeting.

Prefer to talk?(08) 7127 9400Already a customer and need help? Go to Support.
PROPOSED FORM · PRIVATE PREVIEW ONLY

Preview only. Nothing is sent, stored or booked.

A live version will need final routing, consent and privacy review. Subnet privacy policy

Contact us