networks
SaaS · provided and run by Punto Networks

Continuous visibility of your network and its security

NetworkBricks doesn't hand you another list of hundreds of vulnerabilities. It answers what to fix first, why, and with what evidence.

The problem

Too many sources, too little certainty

The day-to-day question isn't how many vulnerabilities there are. It's what to fix first, why, and with what evidence.

Hundreds of vulnerabilities

Version-based lists that never say which ones actually apply to each device.

Scattered information

End of life, contracts and criticality spread across separate spreadsheets.

Stale inventory

Manual records that stop reflecting the real network.

What it is

One platform, several teams that gain

A SaaS platform giving continuous visibility of the network and its security, multi-vendor and evidence-based, so each team can decide what to do first.

Operations

Automatic inventory, backups and target versions.

Security

Vulnerabilities with evidence, hardening and alerts.

Risk

Prioritisation by criticality and a risk register.

Continuity

Verified backups, end of support and contracts flagged ahead of time.

Compliance

ISO 27001, NIST CSF, ENS and evidence for audit.

Management

Executive view, refresh plan and budget.

What sets it apart

Evidence instead of assumptions

01

Evidence, not assumptions

It reads each device's real configuration to decide whether a vulnerability applies, and shows the line that proves it.

02

A single prioritised list

Vulnerabilities, end of life, support contracts and criticality together, instead of several spreadsheets.

03

Inventory from the devices

Taken from the network itself and kept current on its own, with no spreadsheets going stale.

In our own testing

≈ 1/3

of version matches are ruled out once each device's real configuration is read. Your network team works only on what matters.

Illustrative example

Vulnerability in the device's HTTP server

Does not apply · ruled out with evidence

running-config · line 214
no ip http server
no ip http secure-server

Without sufficient evidence, the finding stays visible for review. It is never closed on an assumption.

Vulnerabilities

What actually affects you, with evidence

Four steps across every device in the inventory, every day and automatically.

01

Match

Each device, by model and version, against published vulnerabilities.

02

Verify

It checks the configuration: is the vulnerable feature actually enabled?

03

Evidence

When it is ruled out, it shows the configuration line that proves it.

04

Review

Without sufficient evidence it stays visible. It is never closed on an assumption.

Sources, daily and automatic

Vendor advisories
Cisco, Palo Alto and Fortinet
NVD
Several times a day
CISA KEV
Known exploited vulnerabilities
The platform

Seven modules, one shared inventory

They all work off the same inventory, which is why the information stays consistent across screens. The home panel gives the overview; each module has its own technical view for day-to-day work.

Inventory

The common base of the whole platform: information stays consistent across screens.

Monitoring

Device status.

Security

Vulnerabilities and bugs.

Intelligence

Vendor advisories and AI.

Configuration

Backups, hardening and access.

Lifecycle

End of support, contracts and refresh.

Compliance

Regulatory frameworks and evidence.

Multi-vendor

Your whole estate in a single view

Full collection

  • Cisco
  • Palo Alto Networks
  • Fortinet
  • Juniper
  • Arista

Identified in the inventory

  • Huawei
  • Aruba / HPE
  • Other vendors

The final list is agreed during the survey, based on your estate.

Architecture and security

No open ports into your network

A lightweight collector inside your network connects outbound only. Nobody comes in from the internet.

Collector
A Linux virtual machine: 1 vCPU, 1 GB of RAM and 2 GB of disk. Installed in minutes.
Towards your devices
SSH and SNMP, read-only. Query commands only; it never changes a configuration.
Towards the platform
Outbound HTTPS 443. No inbound connections into your network.
Encryption
End to end between collector and platform; configurations are stored encrypted.
Credentials
In an encrypted vault, never visible on screen.
Hosting
A dedicated instance per client, in the region you agree.
Data and artificial intelligence

Your data, under your control

  • A dedicated instance per client, in the agreed hosting region.
  • The data is yours: at the end it is handed over and the instance is securely deleted.
  • Administrator, engineer and reader profiles.
  • Audit log: every change and every view or download of a configuration.
  • AI researches vendor advisories, proposes analysis rules and drafts summaries.
  • An assistant answers questions about the state of the network.
  • Nothing changes without approval from someone on your team.
Network governance

Access, diagrams and risk kept current

Access review

It extracts local accounts and their privileges from each device. Your team approves or flags for removal, one by one or in bulk, and the evidence is kept for audit.

Diagrams and topology

A per-site diagram repository with version history, plus a topology discovered on its own from neighbours and adjacencies.

Risk register

Impact, likelihood, mitigation, owner and date. The platform proposes risks from what it detects; your team decides which to register.

Compliance and integrations

From finding to action

Compliance
ISO 27001, NIST CSF, CIS Controls, ENS and GDPR, assessed against real data with evidence of access, backups and hardening.
Tickets
Every relevant finding raises an event that becomes a ticket in ServiceNow or Jira: a critical vulnerability, end of support approaching, a contract about to expire or a hardening deviation.
Alerts
Microsoft Teams, webhooks and email, filtered by criticality so each team only gets what concerns them.
Reports and API
Executive PDF report, technical views and exports. REST API with per-role keys and a Zabbix integration.
Managed service

We run it; you decide

Punto Networks provides, runs and maintains the platform. Very little is needed on your side.

What you provide

  • A lightweight collector inside your network.
  • Read-only access to the devices.
  • Depending on scope: a repository for backups and an integration user for your ITSM.
5x8
Support during business hours
48 h
Maximum response time for requests
1/month
Service management report

New versions of the platform are rolled in as part of the service.

Rollout

In stages, with nothing to redesign

Stage 1

Platform available

Within days, run by Punto Networks.

Stage 2

Discovery

The collector discovers by network range; also by IP or from a spreadsheet.

Stage 3

Waves

Onboarding by site or by vendor, plus the integration with your ITSM.

Stage 4

Pilot period

Tuning rules, reports and alerts with your team before continuous operation.

Scale
3,000 devices and beyond: collectors are added at new sites, with nothing to redesign.
Collectors
Typically one per country or data centre, plus one more at large sites.
Live inventory
Once loaded, it keeps itself up to date.
Commercial model

One service, everything included

36

month contract

Over the agreed device range.

Included in the service

  • Support
  • Platform updates
  • Infrastructure

Terms for growth or reduction, and the commercial detail, go in the proposal.

Proof of concept

Try it on your own network

Your own devices, vulnerabilities and configurations in the platform, validated with your team before you decide.

  • 1–2
    representative sites
  • 50–200
    devices, with Cisco, Palo Alto and Fortinet
  • 3–4
    weeks
Week 1

Installation

Collector installed and devices onboarded.

Following weeks

Review and tuning

We review the results with your team and tune rules and alerts.

Close

Results

A results session against the criteria agreed up front.

Scope to fit
If a specific case matters to you, such as a site with devices near end of support, we include it.
Data at the end
You decide: carry it into the rollout, or we delete the instance and document it.
Terms
Agreed before starting, together with the scope and the success criteria.
Next step

Let's start with a demo on real devices

Then we define the scope and criteria for the proof of concept. Whatever is configured during the POC is reused in the rollout.