Three layers of implementation
Buy security as one packaged project and the usual result is a stack of boxes at the edge with a naked internal network. We work in three layers by failure point, each with its own acceptance criteria:
Perimeter: stop the break-in
Next-generation firewall, intrusion prevention, egress traffic audit and hardened remote access. The question is whether policy is tight, and whether any any-any rule has been left open for months.
Internal: stop lateral movement
NAC admission, 802.1X authentication, endpoint compliance checks, VLANs and segmented authority. The question is whether an unknown device can plug in at all, and how far it gets once it does.
Endpoints and data: stop the leak
Anti-virus and patch baselines, peripheral control, data loss prevention, central log retention. This is where the most overlooked element sits: people.
The layers are not parallel — they converge in order. With a sloppy perimeter, a finely segmented internal network is still bypassed; without segmentation, endpoint control is just software somebody installed.
Edge to endpoint: what we actually do
| Layer | What we do | Maps to |
|---|---|---|
| Perimeter | Next-generation firewall deployment and policy governance, intrusion prevention, anti-virus, egress traffic audit | MLPS Level 2 / 3 perimeter requirements |
| Internal network | NAC admission, 802.1X authentication, endpoint compliance checks, segmented authority | MLPS identification and access control |
| Clients | Anti-virus, patch management, peripheral control, data loss prevention | Endpoint security requirements |
| Audit | Central log retention (≥6 months), activity audit, report export | Cybersecurity Law log retention |
| Framework | MLPS assessment support, ISO 27001 implementation, security policy and process authoring | Regulatory inspection and tender qualifications |
We hold ISO 27001 for information security management and ISO 20000 for IT service management, together with H3C Commercial Security (SMB) Elite and 360 Enterprise Security Certified Reseller status. Our ability to deliver security work is on the record.
Compliance: evidence at audit and records that hold up
MLPS assessment is not a one-off exam. What actually stalls projects is the chain of evidence: are policy changes recorded, can logs be traced back, are permissions reviewed on a schedule.
Classification and gap analysis
We confirm the system classification (Level 2 or 3) and walk the controls one by one against reality, producing a gap list with remediation priorities — not an off-the-shelf proposal.
Remediation and hardening
Work proceeds from the gap list: policy tightened, admission live, logs centralised, patch baselines set. Every item leaves a configuration snapshot and a verification record.
Assessment support
We give the assessor topology, configuration, logs and policy documents, and answer questions on site; afterwards the findings are closed out and become the baseline for the next cycle.
Joining the frameworks
MLPS requirements are mapped into the ISO 27001 documents and processes, so one set of policies serves both a regulator and a customer audit — no writing everything twice.
Delivery and ongoing operations
Switching the kit on is only the start. What decides the posture six months later is whether anyone keeps maintaining it — which is why we run this as a service, not a one-off project.
Policy review
Firewall and admission policy are reviewed quarterly to clear temporary openings, expired rules and dormant accounts, so policy does not drift out of control as projects accumulate.
Logs and alerts
Central log retention, tuned alert rules, severity-based notification. More alerts is not better — an alert you can act on is the only useful kind.
Versions and patches
We track vendor security bulletins, assess the blast radius, then schedule a hardening window; changes run through the customer's CAB and stay traceable.
Incident response and drills
We write the incident response plan and run tabletop and live drills with the customer: ransomware, isolating a compromised host, handling a leaked account.
Permission review
Administrator rights and remote access accounts are reconciled quarterly, with access revoked the moment someone leaves or moves — no permissions left to settle.
Reporting and evidence
A quarterly security operations report: incident counts, closed remediation, risk trend — citable directly as evidence in an inspection or a customer audit.