Architecture & Compliance
Architecture & compliance
This page is written for technical evaluation, procurement and security review. Capability attribution, component licenses, and implemented versus outstanding security controls are listed explicitly.
01 / Layers
Four layers, attribution per layer
Operations layerIn-house
cockpit / analyticsalarm clusteringticket state machineinspectionVQA rulesasset registryAI rules / repair wizardRBAC / sessionsaudit hash chain
Video accessUpstream
wvp-GB28181-proZLMediaKitGB28181-2016 signallingRTP / RTSP / RTMPregistration / heartbeat / subscribe
Runtime & deliveryBase
Node.js ≥ 18Nginx gatewayDocker / Compose or systemdatomic JSON persistence
OptionalOff by default
Tencent Map GL JS (own key)LLM gateway (redacted text)ONVIF (non-open-source, licensed)
| Layer | In-house? | Evidence | Approved wording |
|---|---|---|---|
| Operations business | 100% | Tickets, inspection, VQA, assets, analytics, AI rules, audit and RBAC are implemented and tested in this repository, with zero npm runtime dependencies. | “Core operations layer, 100% in-house” |
| Video access | Upstream | GB28181 signalling, registration and streaming are provided by the upstream; this project integrates via a REST adapter without altering upstream marks. | “Built on wvp-GB28181-pro (MIT)” |
| Runtime | Dependency | Node.js, Nginx and Docker are runtime dependencies, not product code. | “On-premise, no npm runtime dependencies” |
| AI | In-house rules | Clustering, advice, risk, Q&A and review are local rules; an LLM is optional and off by default. | “Local-first AI, no external calls by default” |
| Map base layer | Third party | Optional satellite base map; the schematic mode has zero network dependency. | “Offline schematic map, optional satellite layer” |
02 / Licenses
Components and obligations
Each third-party component is documented with its name and version, license and source, and runtime location. Upstream license texts are not yet bundled in the repository — closing that gap is required before delivery.
| Component | Version / Source | License | Runtime location | Obligation |
|---|---|---|---|---|
| wvp-GB28181-pro | master · github.com/648540858/wvp-GB28181-pro | MIT · © 2020 swwhaha | Separate service container; accessed via REST adapter | Retain LICENSE and copyright; ship MIT text with derivatives; attribute the upstream |
| ZLMediaKit | official image / master | MIT + supplementary term | Media service deployed with wvp | Do not remove the “ZLMediaKit” mark from title / Server / User-Agent |
| Node.js | ≥ 18 | MIT | Operations service process | Include license text when distributing images or packages |
| Nginx | 1.24+ (this site: 1.30.6) | BSD-2-Clause | Reverse proxy, TLS, rate limiting | Retain copyright notice; not distributed with the product |
| Tencent Map GL JS | optional, own key | Tencent terms | Browser only, satellite mode | Referer allowlist; key never in repo or front end; automatic fallback |
| ONVIF access | non-open-source | Separate license | Not included by default | License separately or use GB28181 access |
| DADI-OPS code | v0.1.0 | UNLICENSED (EULA pending) | Business service and front end | Define commercial license before public release |
Version pinning and image scanning are not yet complete. The upstream is deployed from master or the official image without digest pinning, and there is no CI image scan or dependency review. Both should be added before production delivery, together with a
licenses/ directory in the package.
03 / Security
Implemented controls
| Control | Implementation | Status |
|---|---|---|
| Authentication | Password login, scrypt + random salt, lockout, session TTL | Implemented |
| Access control | Three roles; method + path permission matrix enforced server-side | Implemented |
| Transport security | TLS 1.2/1.3, HSTS, CSP, HTTP redirect | Template ready; enable on site |
| Request surface | Static allowlist, path traversal rejection, 64KB body cap, CORS allowlist | Implemented |
| Brute force | Account lockout plus 10 requests/minute at the gateway | Implemented |
| Audit integrity | SHA-256 chain, breakpoint location, external anchor parameter | Partial: independent storage and daily anchoring pending |
| Container hardening | Non-root, cap_drop ALL, no-new-privileges, read-only root, healthcheck | Implemented |
| Backup and health | gzip + SHA256 + rotation; exit codes for monitoring | Implemented |
| Storage encryption | Business data is plain JSON; passwords are hashed only | Not implemented |
| Off-site backup / restore drill | Local directory only, no restore script | Not implemented |
04 / Boundary
Delivery boundary and known gaps
The current release is a prototype and pilot delivery. MLPS level 3 conclusions must come from an accredited evaluator; the items below are the engineering self-assessment.
| ID | Item | Status | Requirement before launch |
|---|---|---|---|
| G-01 | Bundle licenses and NOTICE in package/image | Open | Archive wvp, ZLMediaKit, Node.js and Alpine license texts |
| G-02 | Per-person accounts or SSO / LDAP | Open | Replace shared role accounts; keep an account registry |
| G-03 | Password complexity and rotation | Open | Enforce length/complexity and 90-day rotation |
| G-04 | Independent audit storage + daily anchoring | Chain implemented | Write the chain head to read-only / WORM storage |
| G-05 | Audit retention ≥ 6 months | Open | Raise retention or export to a log platform |
| G-06 | Digest pinning and image scanning | Open | Pin base images; add CI scanning |
| G-07 | Storage encryption | Open | Disk/volume encryption or field-level encryption |
| G-08 | Off-site backup | Open | Object storage or cross-host replication |
| G-09 | Restore script and quarterly drill | Open | Provide restore tooling and keep drill records |
| G-10 | Commercial license (EULA) | Pending | Legal decision and delivery with the package |
| G-11 | Upstream notice in product UI | Partial | Add to About / Settings |
| G-12 | Row / zone level permissions | Open | Authorisation down to zone and device group |
| G-13 | SIEM / central monitoring | Open | Integrate central logging and alerting |
| G-14 | Free-text personal data policy | Open | Publish guidance for alarm and ticket notes |
What we do not claim: “100% in-house”, “MLPS level 3 certified”, “large-scale commercial deployment”, “AI auto-remediation”, or “face and plate recognition”. Video frames, faces, plates and movement patterns are sensitive personal information; this system does not store video streams or perform face recognition. Any future capture capability requires separate consent, retention limits, access audit and impact assessment.
AI data boundary: zero external requests by default. With an LLM explicitly enabled, only the redacted question, local conclusion and fact card are sent (device names become “site#N”); IPs, GB IDs, asset IDs, personnel, ticket text, images and video frames are excluded. Numbers in the answer must match local facts, otherwise the local conclusion is used. A data processing assessment and agreement are required before enabling it.