Aktualisiert · Version 3
Website · Screenshot dieser VersionText dieser Version anzeigen
DataBase Leaked
[Link entfernt]
[Link entfernt]:[Link entfernt]@securitas.fr:sDAYyeUSwf6SRv
The files will be published after the timer counts down. The company still has time to get in touch with us
[Link entfernt] 92 GB DataBase
1. EXECUTIVE SUMMARY
The RVS Software archive contains software and technical materials for deploying, connecting, configuring, and supporting video security systems. The dataset totals 92.04 GB across 15 product and technical groups, with 175 delivered packages, documents, and supporting files and 24,247 counted entries inside packages and disk images.
Development materials appear in several forms. SQL, PowerShell, shell, batch, XML, JavaScript, and embedded JScript contain readable implementation or configuration text. Windows applications contain .NET intermediate code, AxisInstaller contains Python bytecode, and camera and server components contain native machine code. InnoVi virtual software appliances contain analytics executables, neural-network graphs, model weights, container definitions, and a device-management web interface.
PortChecker explicitly identifies internal use within Securitas RVS. Other represented products and components belong to Agent Vi, Milestone Systems, Calipsa, Digital Barriers, The Boring Lab, or AXIS Communications. The archive therefore combines internal RVS utilities and deployment knowledge with third-party product software and integration materials.
The implemented functions cover camera-agent deployment, server-connectivity checks, analytics-event reception, operator incident workflows, PTZ control, rules and digital I/O, schedule management, statistics export, device-availability monitoring, database maintenance, and virtual-appliance administration.
Technical sensitivity comes from the combination of product logic and deployment knowledge. Connection profiles, service relationships, certificate-transfer procedures, authentication settings, camera-management paths, database definitions, model structures, calibration formats, and analytics logic describe how the environment is assembled and how major components interact.
The archive also distinguishes implementation materials from operational data. Empty settings stores describe schemas, report templates define program output, diagnostic tools collect support information, and demonstration scenarios illustrate product behavior. These objects serve different functions from populated client databases, completed incident records, or finished operational reports.
2. BUSINESS CONTEXT
Publicly available company information
Securitas describes its services as guarding, technology, fire and safety, and corporate risk management. The company’s electronic security offering includes video surveillance, access control, intrusion detection, monitoring, and system design and installation.
Official company descriptions:
[Link entfernt]
[Link entfernt]
Software context
The RVS materials relate to the development, configuration, integration, and operation of video security systems. The packages connect camera analytics to management platforms, provide applications for operators and administrators, and automate preparation of cameras, servers, and virtual software appliances.
Several components serve the same environment from different sides. Camera agents process or forward images, analytics services interpret video, software bridges convert analytics results into VMS events, and Smart Client extensions display incidents or graphical overlays. Supporting utilities provide connectivity, configuration, diagnostics, device administration, and availability monitoring.
Top-level groups represent products, vendors, tools, infrastructure, and training areas. They describe the technical environment rather than a list of security-service clients or contract values.
3. DATASET SCALE AND STRUCTURE
Dataset size: 92.04 GB.
Product and technical groups: 15.
Delivered packages, documents, and supporting files: 175.
Entries inside packages and disk images: 24,247.
Total counted entries: 24,422.
Storage size counts each delivered package once. Files contained inside those packages are described as package contents and are not added again to the 92.04 GB total.
Virtual software appliances account for a substantial share of stored volume. Small scripts and utilities occupy much less space but contain detailed deployment procedures, configuration rules, and operational settings.
Executable installers may contain MSI databases, CAB packages, program files, resources, scripts, and additional compressed components. A product can therefore have only a few delivered packages while containing a much larger set of internal software and resource files.
The 24,422 counted entries include delivered files and registered internal contents such as application components, resources, models, scripts, and files inside virtual disk images. This count describes represented objects, not the number of independent software projects.
4. FILE COMPOSITION
Provided packages and supporting files by format:
Format | Files | Size (MB or GB)
ZIP | 34 | 52.41 GB
ISO | 4 | 20.83 GB
EXE | 69 | 15.75 GB
VHDX | 1 | 2.59 GB
BIN | 5 | 337.66 MB
MSI | 7 | 71.39 MB
PDF | 11 | 33.37 MB
ROS | 1 | 6.98 MB
EAP | 2 | 2.80 MB
PPTX | 2 | 2.45 MB
DLL | 2 | 2.11 MB
RFB | 1 | 0.39 MB
VMRS | 1 | 0.08 MB
VMCX | 1 | 0.04 MB
TXT | 14 | 0.02 MB
DOCX | 1 | 0.01 MB
XML | 5 | 0.005438 MB
CONFIG | 1 | 0.001835 MB
XML_ORIGINAL | 1 | 0.001662 MB
PS1 | 2 | 0.001461 MB
HTML | 1 | 0.001269 MB
CFG | 1 | 0.000795 MB
REG | 2 | 0.000668 MB
SZEPRO | 2 | 0.000406 MB
BAT | 1 | 0.000349 MB
URL | 2 | 0.000284 MB
APDPRO | 1 | 0.000279 MB
TOTAL | 175 | 92.04 GB
The combination of formats reflects software delivery and support. Executable packages and MSI files contain Windows applications and services. ZIP and other packages contain software releases, fixes, camera software, and virtual software appliances. VHDX files store operating systems and software environments. Scripts and configuration files define deployment and integration behavior.
Inside packages, DLL and EXE files appear alongside Python bytecode, camera programs in ELF format, web resources, SQL, XML, JSON, calibration files, sample videos, and interface resources. Several formats are specific to individual products, and their purpose is determined in the context of the corresponding application.
The .msg entries are Tcl/Tk interface translations rather than Outlook messages. The DBF prefix in APD Bridge library names is part of the component name rather than a dBASE table designation.
Some installer items have shortened internal names. SQL scripts were classified by confirmed post-installation names and contents, while preserving the relationship between the package item and the file installed from it.
5. THEMATIC COVERAGE
The categories below may overlap because one file may simultaneously relate to a product, an integration, a deployment process, a diagnostic function, and a training exercise.
Internal operations: PortChecker and infrastructure-configuration materials describe connectivity and administration in the RVS environment.
Camera deployment: AxisInstaller, ACAP/EAP packages, and installation scripts provide transfer of programs to cameras, preservation of settings, and startup configuration.
Video analytics: Vi-Agent, SafeZone, and InnoVi provide camera-side or server-side analytics, model definitions, tracking logic, calibration, and event output.
Operator workflows: MAS/Mastermind, VMS plug-ins, and event bridges link incidents, live and recorded video, metadata overlays, maps, and camera-control tools.
Automation and schedules: EventProxy, SavVi Digital I/O, and the calendar tool link messages, camera inputs, output pulses, analytics rules, and temporary schedule changes.
Infrastructure administration: Boring, AXIS Optimizer, Dell materials, and Hyper-V scripts cover devices, services, configuration, availability, and installation.
Structured application data: SavVi SQL, Milestone SQL, SQLite schemas, XML definitions, JSON examples, and report templates describe application records and their processing.
Authentication and trust: FreeRADIUS configuration, certificate-transfer scripts, service-authentication settings, and endpoint profiles describe access and trust relationships.
Testing and support: Diagnostics Tool, Virtual Camera, demonstration videos, calibration examples, and technical manuals are used for troubleshooting, functional verification, and operator or engineer training.
6. INTERNAL UTILITIES AND DEVELOPMENT-MATERIAL FORMATS
PortChecker
The executable D:\[Link entfernt]\RVS Software\PortChecker\[Link entfernt] is a [Link entfernt] Windows Forms utility for checking connectivity in the RVS environment. Its About section states that it is intended for internal Securitas RVS use and names the developer.
The utility provides Operator, Production, and Server modes. It checks TCP connections to the Management Server, Agent Vi, recording servers, directory service, and SQL server according to the selected role. Results can be written to RVS_Testresults.txt.
PortChecker checks network connectivity rather than Milestone or Agent Vi application authentication. The directory-service check uses TCP port 53. Separate port sets exist for primary and optional secondary Recording Servers. Two SQL exception handlers contain a result-formatting error that can output a message stating that port 1433 is open after a failed connection attempt.
Readable program text
The archive includes original textual implementation materials: database scripts, installation scripts, service definitions, batch files, web code, configuration files, and deployment instructions. The SavVi SQL set defines tables, procedures, indexes, upgrades, and maintenance actions. Milestone fixes contain executable SQL text within program resources.
EventProxy contains an embedded Evaluator class in JScript for rule expressions. Linux appliance files include shell scripts, Docker Compose definitions, and systemd units. Windows operational materials include PowerShell and batch commands for software deployment, Hyper-V preparation, and certificate transfer.
Compiled application code
NET applications expose program structure through intermediate code, types, methods, resources, and APIs. AxisInstaller contains Python bytecode from which its execution sequence and camera-deployment behavior can be determined. The InnoVi portal contains built JavaScript and templates rather than the original TypeScript project.
Camera programs and several server components contain native machine code. Symbols, strings, and decoded code paths expose functions for image processing, tracking, event handling, PTZ behavior, model execution, and service communication.
Development materials by functional group
The twenty groups below summarize represented application and engineering tasks. Grouping is by function rather than by individual executable.
Functional group | Represented materials | Confirmed purpose
Securitas RVS PortChecker | Compiled [Link entfernt] logic and application resources | Checking expected server connections for operator, production, and server roles
AxisInstaller | Python bytecode, packaging and configuration logic | Deploying Vi-Agent and configuring startup on Axis cameras
Vi-Agent camera software | ELF machine code, shell, HTML, and JavaScript | Preparing camera frames, tracking image features, and exchanging data with analytics servers
MAS / Mastermind | Managed plug-ins, WCF, and interface resources | Presenting incidents, associated video, and device-control tools in Smart Client
Calipsa connector | Managed integration and PowerShell | Publishing camera alarms for verification and configuring the VMS connection
Milestone EventProxy | Managed service, XML, and embedded JScript source text | Processing incoming messages and states, then routing events and commands
Milestone SQL fixes | Original T-SQL embedded in executable wrappers | Changing event-action visibility and recording-server registration behavior
SafeZone | Machine-code applications, XML parameters, KNP calibration, and media materials | Perimeter analytics, scene calibration, alarm output, and PTZ tracking
SavVi platform and SQL | Delivered client and server components, schema, and migrations | Storing analytics settings, events, objects, and platform state
SavVi PTZ and installation support tools | Machine-code PTZ monitor, managed utilities, and deployment logic | Coordinating manual PTZ control and maintaining platform installation and settings
Agent Vi / InnoVi MIP plug-ins | Managed event and metadata adapters | Converting analytics results into Milestone events and visual overlays
InnoVi / Irisity Edge | Machine-code analytics, Go backend, built web code, graphs, and model weights | Running edge analytics, managing the appliance, and connecting it to Core
SavVi Digital I/O | Managed service and clients, empty SQLite structure | Linking Axis inputs, output pulses, rules, and calendars
Standalone SavVi utilities | Managed applications for rules, recording, and statistics | Importing analytics settings and exporting received images and statistical results
Milestone Diagnostics | Managed diagnostic application and SQL queries | Collecting selected system, service, and platform information for support
Boring Server / Toolbox | Managed services and APIs, web resources, SQL, and templates | Administering devices and storage, monitoring availability, and generating notifications
AXIS Optimizer | Managed device and search integrations | Adding device control, metadata search, and panoramic viewing tools to the VMS
AXIS Perimeter Defender Bridge | Managed bridge and client display components | Mapping perimeter events and metadata to cameras, alarms, and video overlays
AXIS Virtual Camera | Managed emulator and help files | Providing a live or prerecorded stream through a camera-like interface for testing
RVS deployment and access settings | PowerShell, batch files, XML, CFG, REG, and FreeRADIUS settings | Preparing virtual infrastructure, trust settings, and device-management profiles
Readable SQL, scripts, configuration, and interface code coexist with managed and native compiled applications. Vendor ownership and RVS internal designation are kept separate in the product descriptions.
7. CAMERA DEPLOYMENT AND CAMERA-SIDE ANALYTICS
AxisInstaller
AxisInstaller accepts a single camera address or a list of camera addresses, uploads Vi-Agent over FTP, prepares configuration, and configures startup. Depending on the camera environment, it modifies inittab or uses SSH and systemd to place, enable, and verify the service.
The program supports HTTP Basic and Digest authentication, port settings, PTZ parameters, resolution, and operator-specified agent parameters. Three delivered releases, 1.20, 1.21, and 1.22, each contain 25 application-specific Python code objects. Releases 1.20 and 1.21 use Python 2.7 and py2exe; 1.22 uses Python 3.8 and PyInstaller. Changes include exception handling, UTF-8 processing, Python API updates, and SSH-state verification.
Vi-Agent camera packages
Twelve camera packages contain twelve ELF executables and supporting text or graphics files: ten SavVi packages and two InnoVi EAP packages. Their implemented functions include image acquisition, background estimation, motion processing, KLT feature tracking, camera-movement heuristics, and data exchange with analytics servers.
Two InnoVi MIPS packages contain AxisMipsCloudViAgent, an update script, and a local HTML/JavaScript settings interface. The script checks compatibility and transfers configuration and startup state. The interface exposes camera and agent information, server and proxy settings, and connection status through [Link entfernt].
Builds 100.1.3423 and 100.1.5581 differ in a null-controller check in VIAgent_GetAgentStatus and additional image-storage lifecycle handling. In build 100.1.5581, tracking logic removes static or outlier KLT points, recalculates object boundaries, maintains speed history, detects camera movement, prepares bounded image regions for secondary classification, and exchanges structured feature data with the server through a six-state connection controller.
The KLT frame-processing path swaps frame buffers, replenishes tracked points, applies masks, updates motion estimates, and prepares point records. Tracking state can be reinitialized when no valid points survive. The command dispatcher includes a working JPEG-retrieval path, while its generic GET_FRAME command is a logging stub. Frame-error handling uses a counter and time condition before channel reset, while unexpected event sequence numbers produce a warning but do not prevent forwarding.
SafeZone delivery and calibration
The main CAB in the SafeZone-edge installer contains 484 program and supporting files, including machine-code components, multimedia and interface libraries, nine camera packages, and demonstration materials. The camera packages include the APD PTZ AutoTracking component delivered under the internal name LAST_PTZ_PACKAGE.
GENIUS_PARAMETERS contains segmentation, classification, DNN, tracking, state-management, and people/vehicle size-model settings. Its decoded XML contains 462 elements, including 404 leaf values and 57 groups. Fifteen sensitivity sets cover different lighting and image conditions.
Twelve KNP calibration files contain 1,640 XML elements in total. They define intrusion zones, human-observation areas, manually specified calibration segments, camera matrices, and PTZ mappings, together with seven embedded JPEG or PNG images. These files connect image coordinates and scene geometry to analytics rules and camera movement.
SafeZone analytics and PTZ functions
SafeZone code implements image acquisition from Axis cameras, image-format conversion, background learning, intrusion, presence, and crossing handlers, alarms, metadata, and graphical overlays.
Object tracking uses Kalman prediction and correction, class history, displacement, direction, shape estimates, configurable size and region filters, and day/night models based on mixtures of up to twenty Gaussian components. Class history stabilizes transitions between object types, while UNKNOWN candidates can preserve an established class.
Calibration converts between image coordinates and world coordinates using stored camera matrices and floor-plane geometry. PTZ functions use overview and pan/tilt calibration to convert object coordinates, issue movement and zoom commands, and return the camera to its home position.
Trajectory and day/night logic contains explicit thresholds, fallback calculations, accumulated history, and state-reset conditions. These functions show how the delivered component combines scene calibration, temporal tracking, object classification, and camera control in perimeter-analytics workflows.
8. INNOVI EDGE, MODELS, AND DEVICE MANAGEMENT
Virtual software appliance architecture
The InnoVi virtual software appliances combine Analytics Service and Device Manager. Docker metadata links these roles to delivered builds, including Analytics 2.1.2969 with Device Manager 2.1.1232, Analytics 2.1.4218 with Device Manager 2.1.1296, and Analytics 2.1.6780 with Device Manager 2.1.1701.
Product files sit alongside host installation scripts, network handling, service definitions, container configuration, and the web interface used to administer the appliance.
Neural-network and classification materials
Eight XML graphs in the InnoVi 1.6 materials describe standard and thermal object detection, clothing color, vehicle color, and object-comparison representations. personColor provides fourteen upper-body and fourteen lower-body clothing labels, while vehicleColor provides eight vehicle-color labels.
The comparison models use different output dimensions: sameDiff outputs