3manager WhitePaper DataCollector
3manager WhitePaper DataCollector
Documentation
https://www.dropbox.com/scl/fi/gltegghdm15g9psasqgjo/3manager-WhitePaper-DataCollector-
EN.pdf?rlkey=xlta9799xg0rzu08vaqk4wh20&dl=1
Table of content:
Introduction 3
Network traffic 7
Network diagram 8
Webhooks 13
Security 21
Hosting 22
Ports used:
The data collector will scan printers using port 161/162 which are the standard ports for SNMP communication.
SNMP V1-2
As default the SNMP community string is public. For many printers they either have the string entered or its blank.
In 3manager as default public is used. If you are using a different community string simply overwrite the public. If
you are using multiple you can enter them with comma as separators like this: public, private1, private 2, private 2.
This will force a discovery in each community and discover devices based on how they are configured.
SNMP V3 makes it possible for the SNMP communication to protected by encryption as well passwords. Please
note that the SNMP v3 options depends on the manufacturer brand and model as well generation. The newer
devices, the more options, the older the less.
• Username
• Authentication password (Passwords should have minimum 8 characters)
• Privacy protocol password (Passwords should have minimum 8 characters)
• Context name
Important:
The 3manager data collector will automatically find the settings for encryption. For example if AES or DES is used.
You do not need to configure this in the data collector. If privacy protocol is not used leave the password field
blank.
You can have mixed environments using SNMP v1-2 and SNMP v3. This means that you can use the same data
collector to scan older devices without SNMP v3 support as well new ones with updated SNMP v3 capabilities.
Communication
The data collector will download the latest data to ensure correct counter readings from the printers. This is done
for every discovery and polling session. Ports used are either port 80 or port 443 depending on your configured
settings. Default is always port 443
1. Download of configuration (IP-ranges which is managed online, and other settings such as scheduling)
2. Download of latest OID (the keys to know where to find the correct counters in your printers)
In some occasions whitelisting of IP and domain will be needed. Use the following values:
• Domain: *.3manager.com
• IP-address: 52.213.181.35
Delivery methods:
• Manufacturer brand
• Model name
• Serial number
• Counters (total pages, total mono, total color, total print, print mono, print color, A5 total, A3 totals)
• Toner levels
• Alerts
• Warnings
The data collector uses a Certificate from COMODO 256-bit SSL encryption when sending data over the Internet.
The transaction between user and server is encrypted as well as the data sent from the data collector agent to the
server.
Outgoing traffic:
Discovering:
During discovery, the agent sends packets to each IP in the specified range. It sends about 500-800 packets a
second, with a packet size 85-100 bytes. Total bandwidth used is 50-200KB/s. The total data sent will depend on
the IP address count in the discovered IP range(s).
Polling:
During polling, the agent only sends packets to the printers discovered in the network discovery process.
There is one HTTP request by the configuration server for each printer 1-10KB in size. SNMP query count depends
on the printer, but it ranges in 15-50 queries with 1-5KB in size, total bandwidth used is 15-250KB for each printer.
The polling is done with 40 threads in parallel, the total bandwidth depends on the printer response time and is
about 0.5-1MB/s (needs to be measured onsite, for more precise time)
Frequency:
The data collector gets status updates every 15 minutes. Technical data, meters and toner status will be updated in
this frequency. The agent scans devices using SNMP protocol. The data is sent as UDP packets.
The service also connects to remote servers using HTTP(s) to get latest configuration.
Reporting:
Report size is proportional to discovered printer count. Each printer uses ~10KB of data. The data is sent as JSON
over HTTPS to the 3manager Data Processing Server (DPS). Reports are sent hourly by default.
Auto update can be disabled in the agent control panel settings if this is a violation to the security policy.
Download latest data collector from your account run it on the same computer where current data collector is
installed.
This will update the software to the latest version. You can also use this link to send to customers who will install
the data collector internally. (Remember to provide the location-ID)
Windows: Microsoft Windows based computer (XP SP3 or newer / 2003 Server or newer)
Microsoft .NET Framework 4.6 or newer. For the web-version Microsoft .NET Core is used and
contained in the installation package. Here you do not need to have .NET Framework 4.6 or
newer.
Linux x64: The data collector works with common Linux distros such as Ubuntu, Debian, CentOS and
more). 64bit only
Browsers: Google Chrome, Safari, Firefox, Microsoft Edge. Internet Explorer 11 or newer.
Hardware: The data collector requires minimum of 10GB free hard disk drive and 4GB RAM with Internet
access. It’s not recommended to install the data collector on laptops as it may scan other
networks. If a computer is not available for installation, we recommend using a Raspberry Pi 3
model B or newer with a minimum of 16GB SD card.
Proxy: If proxy is used, user and password is needed to access the 3manager server. HTTP 1.1
compliant proxy server, domain proxy and PAC file compiled proxy is supported.
SNMP: SNMP enabled. (Minimum V1-2). SNMP v3 is supported. Minimum lengths of passwords is 8
characters when configuring the SNMP V3 on the printers.
Only device information is sent. No data regarding print jobs or usernames are collected nor sent.
A webhook is a method used to provide real-time information to other applications. It's essentially a
way for an app to send automated messages or information to another app when a specific event
occurs. Instead of requesting data from a server, the server pushes the data to the client automatically,
making webhooks a form of "reverse API call."
Add the URLs for equipment reports (typically used for billing) and alerts (the supplies, service codes
etc)
• Equipment reports. (Anything you want to configure as a report can be pushed to the
equipment endpoint.
• Alert profile: Any alert created based on your profile will be pushed to the alerts end point
IMPORTANT:
The webhook integration will only be active on the same vendor level it was added. This means that if
you have sub vendors you would like to use the webhook, you need to enable the integration on those
levels too.
{
"type": "SupplyAlertTriggered",
"alert": {
"accountId": "d78bc0fd-4eef-4092-b713-d6f668cd380f",
"deviceId": "4a8df93d-d560-4a2b-bfb2-1036774bea20",
"deviceName": "Demo Device 129",
"manufacturerName": "Hewlett-Packard",
"modelName": "Color LaserJet flow MFP M880",
"ipAddress": "10.47.80.143",
"serialNumber": "SN0015",
"colorant": "black",
"supplyType": "TonerCartridge",
"partNo": "CF300A",
"supplyDescription": "Black Cartridge HP 827A (CF300A)",
"location": "??",
"contractName": "HP (Estimated)",
"organizationalUnitName": "MPS Demo Customer",
"departmentName": "Department 1",
"threshold": 0.8,
"emptyInDaysThreshold": 80,
SQL injection refers to an injection attack wherein an attacker can execute malicious SQL statements (also
commonly referred to as a malicious payload) that control a web application’s database server (also commonly
referred to as a Relational Database Management System – RDBMS).
Since an SQL injection vulnerability could possibly affect any website or web application that makes use of an SQL-
based database, the vulnerability is one of the oldest, most prevalent and most dangerous of web application
vulnerabilities.
SQL injections can happen in places where a SQL query with parameters from web user interface is formed in
code. In 3manager we manage this differently.
We send the SQL query template and parameters from user interface to the SQL servers separately, and on the
servers its combined to the final query in a secure way.
This is a common issue for non-Microsoft developed applications, and basically, the defender says “It's not
developed by Microsoft, so we can't say if this is good or bad”.
You can safely continue installing the software by choosing “More information” and then continue.
If you are using other antivirus systems, you will probably not get any warning at all.
This URL shows the check-result from all major antivirus providers scanning 3manager software:
https://www.virustotal.com/gui/file/de52d9fed7d0db6b13a5905768c97b17ccef9f1c15be8b64527799f90e146a35/d
etection
Symptoms:
• The data collector stops working and you see a warning saying “A root element is missing”.
• Your antivirus systems detects the data collector as a trojan horse
• .exe files are deleted preventing any update of the data collector
• You cant install the data collector
Resolution:
Add exclusions for the 3manager data collector agent by following the guidelines in the documentation provided
by your antivirus system provider.
If an Antivirus product has quarantined 3manager files and/or removed it, you may have to install the data
collector again, but first you need to delete the printer agent folder completely BEFORE you run the new
installation.
c:\users\all users\printeragent
c:\users\all users\application data\printeragent
c:\appdata\printeragent
The 3manager data collector uses a 256bit encryption comodo certificate and is signed as well, meaning that the
publisher is 3manager and the software hasn’t been altered from being downloaded online to being installed.
When real-time protection interacts with network services like SNMP queries, the antivirus may treat
the traffic as suspicious and intensively scan it, causing CPU spikes.
3manager performs regular SNMP queries to monitor devices. These queries occur during polling,
which happens every 15 minutes, and discovery, which runs every 8 hours. If the antivirus scans these
frequent queries, it can significantly contribute to increased CPU usage.
CPU usage can rise due to the antivirus software scanning every action performed by critical
applications. For 3manager, real-time protection may continuously analyze SNMP query-related
processes, such as:
This increased scrutiny can slow down system performance, especially if these processes are scanned
frequently.
To reduce CPU load, it’s essential to exclude these 3manager processes from real-time protection. This
prevents the antivirus from constantly scanning them, allowing the system to run smoothly.
If excluding these processes doesn’t resolve the issue, please contact 3manager support for further
assistance.
We rely on AWS's robust security infrastructure and certifications to protect our hosted environment.
AWS maintains a comprehensive set of security measures, including physical security, network security,
and data encryption, to safeguard our data and infrastructure. Check more about hosting security on
page 21.
OS Updates
We continuously monitor and assess operating system updates, applying only those that are relevant
to security. This targeted approach ensures that our servers are protected against known security
vulnerabilities while minimizing potential disruptions to our system's stability.
Access to our servers is restricted to authorized personnel only. Only developers and database
managers have access. We enforce this through strict access control measures, ensuring that only
individuals with a legitimate need have access to our systems.
To enhance security, we enforce two-factor authentication for all personnel accessing our servers. This
additional layer of security helps prevent unauthorized access, even in the event of compromised
credentials.
IP Whitelisting
We further secure our servers by implementing IP whitelisting, which restricts access to specific IP
addresses or ranges. By allowing access only from trusted sources, we reduce the likelihood of
unauthorized access attempts from malicious actors.
Our servers do not have any third-party tools installed, and they are not used for web browsing or
email management purposes. This minimizes the attack surface and reduces the risk of vulnerabilities
introduced by external software.
Hosting
The 3manager servers are hosted in Europe (Ireland, South Dublin, Greenhilss Road, Tymon North,
Dublin) at Amazon. (AWS).
Certifications:
Environment:
Security:
Network:
• Datapipe network features redundant fiber sources and redundant aggregate switches and core routers
• Direct BGP peering with five Tier 1 providers; BTN, Interoute, Level 3, Tiscali, and T-Systems
At 3manager, we have a robust disaster recovery process in place to ensure business continuity and
data integrity in case of system failures or catastrophic events. Our process is built around AWS’s
scalable infrastructure and includes both automated backups and well-defined recovery procedures.
Backup Strategy:
Daily Incremental Backups: We perform daily incremental backups of all critical data. This ensures that
only the changes made since the last backup are stored, minimizing backup size and reducing recovery
time.
Every week, we perform a full backup of all data, capturing the entire state of our system. This allows us
to have a complete and up-to-date snapshot of our data available for recovery.
All backups (both incremental and full) are securely stored in a third party location, with encryption
enabled and only available for 3manager development team for access.
To ensure maximum availability and protection against regional failures, backups are replicated across
multiple regions.
Step 1:
Identify the most recent incremental or full backup to be restored, based on the timing of the disaster.
Step 2:
Launch a new instance or restore the affected systems using AWS depending on the affected
components.
Step 3:
Retrieve and restore data from the backups. We first apply the most recent full backup, followed by
incremental backups to ensure minimal data loss.
Step 4:
Conduct system validation to ensure all services are up and running properly, and no data is lost.
Step 5:
• Notify stakeholders once the recovery is complete and all systems are operational.
• Recovery Time Objective (RTO) & Recovery Point Objective (RPO):
• RTO (Recovery Time Objective): Our goal is to have systems fully operational within 8-12 hours
of identifying an incident, depending on the scale of the failure.
• RPO (Recovery Point Objective): With daily incremental and weekly full backups, we aim to limit
potential data loss to within 24 hours of the most recent incremental backup.
Monitoring:
Automated monitoring is in place to detect potential issues early, minimizing downtime and speeding
up the recovery process.
o If proxy server is used it might also report issues. We recommend adding the proxy server, user and password
in the data collector during installation if used.
o White list the URL: *.3manager.com. If it's not allowed to whitelist the domain then the following needs to be
whitelisted: services.3manager.com, modelapi.3manager.com, cloudmibwalkapi.3manager.com
o In case it's needed to enter the IP address of the data processing server its: 52.213.181.35. This is the server
where the data collector sends data, activate the license and ask for updates.
o Internally the 3manager data collector will use port 161/162 to communicate with the printers. These are in
most cases already open. If they are not the printers will not be visible for monitoring.
o SNMP version 1 & 2 or 3 needs to be enabled on the printer or it will be invisible for the data collector. Unless
changed, printers are default having SNMP v1-2 enabled.
o If CPU Usage is too high, please go to the section with CPU Usage and Real Time Protection to learn more
about whitelisting of the SNMP processes.