DADI-OPS v0.1.0 · Prototype and pilot delivery; interface data is illustrative Delivery boundary & compliance →
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.

wvp-GB28181-pro (MIT)zero runtime npm depsnon-root containerengineering self-assessment
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 conclusion table — the approved external wording
LayerIn-house?EvidenceApproved wording
Operations business100%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 accessUpstreamGB28181 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)”
RuntimeDependencyNode.js, Nginx and Docker are runtime dependencies, not product code.“On-premise, no npm runtime dependencies”
AIIn-house rulesClustering, 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 layerThird partyOptional 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.

ComponentVersion / SourceLicenseRuntime locationObligation
wvp-GB28181-promaster · github.com/648540858/wvp-GB28181-proMIT · © 2020 swwhahaSeparate service container; accessed via REST adapterRetain LICENSE and copyright; ship MIT text with derivatives; attribute the upstream
ZLMediaKitofficial image / masterMIT + supplementary termMedia service deployed with wvpDo not remove the “ZLMediaKit” mark from title / Server / User-Agent
Node.js≥ 18MITOperations service processInclude license text when distributing images or packages
Nginx1.24+ (this site: 1.30.6)BSD-2-ClauseReverse proxy, TLS, rate limitingRetain copyright notice; not distributed with the product
Tencent Map GL JSoptional, own keyTencent termsBrowser only, satellite modeReferer allowlist; key never in repo or front end; automatic fallback
ONVIF accessnon-open-sourceSeparate licenseNot included by defaultLicense separately or use GB28181 access
DADI-OPS codev0.1.0UNLICENSED (EULA pending)Business service and front endDefine 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

ControlImplementationStatus
AuthenticationPassword login, scrypt + random salt, lockout, session TTLImplemented
Access controlThree roles; method + path permission matrix enforced server-sideImplemented
Transport securityTLS 1.2/1.3, HSTS, CSP, HTTP redirectTemplate ready; enable on site
Request surfaceStatic allowlist, path traversal rejection, 64KB body cap, CORS allowlistImplemented
Brute forceAccount lockout plus 10 requests/minute at the gatewayImplemented
Audit integritySHA-256 chain, breakpoint location, external anchor parameterPartial: independent storage and daily anchoring pending
Container hardeningNon-root, cap_drop ALL, no-new-privileges, read-only root, healthcheckImplemented
Backup and healthgzip + SHA256 + rotation; exit codes for monitoringImplemented
Storage encryptionBusiness data is plain JSON; passwords are hashed onlyNot implemented
Off-site backup / restore drillLocal directory only, no restore scriptNot 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.

IDItemStatusRequirement before launch
G-01Bundle licenses and NOTICE in package/imageOpenArchive wvp, ZLMediaKit, Node.js and Alpine license texts
G-02Per-person accounts or SSO / LDAPOpenReplace shared role accounts; keep an account registry
G-03Password complexity and rotationOpenEnforce length/complexity and 90-day rotation
G-04Independent audit storage + daily anchoringChain implementedWrite the chain head to read-only / WORM storage
G-05Audit retention ≥ 6 monthsOpenRaise retention or export to a log platform
G-06Digest pinning and image scanningOpenPin base images; add CI scanning
G-07Storage encryptionOpenDisk/volume encryption or field-level encryption
G-08Off-site backupOpenObject storage or cross-host replication
G-09Restore script and quarterly drillOpenProvide restore tooling and keep drill records
G-10Commercial license (EULA)PendingLegal decision and delivery with the package
G-11Upstream notice in product UIPartialAdd to About / Settings
G-12Row / zone level permissionsOpenAuthorisation down to zone and device group
G-13SIEM / central monitoringOpenIntegrate central logging and alerting
G-14Free-text personal data policyOpenPublish 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.