Connect
Add a switch with its address and credentials. The platform is detected on connect.
A console for the access layer. It reaches your switches over SSH, keeps a live picture of ports, VLANs, neighbours and hardware, lets operators change port and VLAN configuration behind preview, confirmation and an audit trail, and records who appeared on which port and when it changed.
Add a switch with its address and credentials. The platform is detected on connect.
Ports, VLANs, neighbours, MAC tables and hardware health arrive and stay current.
Edit a port or VLAN, read the preview of what will be sent, confirm, and the change is recorded.
A new host, a moved host or a lost neighbour becomes an event, forwarded where it is needed.
A poller keeps each switch current: port status and description, traffic rates, error counters, VLAN membership, LLDP neighbours, MAC table, power, fans, temperature, CPU, memory and logs.
Port and VLAN edits are shown as a preview of what will be sent, applied only after explicit confirmation, and recorded in an audit trail. Saving to startup configuration is a deliberate, separate action.
Neighbours, port channels and hosts seen only behind a device are drawn as one map, with several links onto the same wire folded into a single segment rather than shown as separate connections.
Every MAC learned on the access layer becomes a host that can be named and approved. A new host, a host that moved to another port or switch, and a neighbour that disappeared are each recorded as an event.
Access events leave as RFC 5424 syslog to SDefender and as tickets to SDefender Desk, so a change at the port shows up where the security team already works.
A multi-switch dashboard, scheduled e-mail reports, roles, sessions and HTTPS from the first install, so the console is safe to leave running.
What is connected where, at what rate, with what errors, and which VLANs it belongs to.
Who changed which port or VLAN, what was sent to the switch, and when.
Hosts appearing, moving between ports and switches, and links coming and going, exportable and available over an API.
Every physical port on every managed switch is counted: how many carry a link, how many are enabled with nothing plugged in, and how many have been idle long enough to reclaim — per switch and by port type, exportable as CSV.
Documentation capture. Switch names are blurred.
Access control here means seeing and recording who is on the network and what changed, and handing that to the systems that act on it. Blocking a port from an incoming API is on the roadmap and is not claimed as shipped.
Dell Networking OS6 and OS9, Cisco IOS, HP Aruba and Juniper are driven over SSH and validated against real hardware, not only a simulator. The platform layer is shared, so a further switch family is added in one place — tell us which one you run.
The console records and reports access changes. It does not yet block a port or quarantine a host on its own.
A switch from a platform outside the supported list can be inventoried but not managed.
Where a platform driver is read-only, the write forms for that switch are hidden rather than offered and failed.
Connect a single switch, confirm the live picture matches the device, then widen to the access layer.
One switch, read-only first, to confirm the picture is right.
Add the rest of the access layer and name the hosts that matter.
Point access events at SDefender and SDefender Desk.
Hand routine port and VLAN work to operators, with preview and audit in place.
Choose one product, one environment and one measurable outcome. We define success criteria before the engagement begins.
Tell us a bit about your environment and we'll get back to you shortly.
Your message has reached us; a member of the SDefender team will be in touch shortly. You're always welcome to reach us directly at info@sdefender.com.