Secure and high-performance usage of Web Port is essential for protecting sensitive data, preventing slow performance, and ensuring a stable, reliable user experience. By following industry-proven security and performance best practices, customers and partners can reduce security risks, avoid performance bottlenecks, and maintain optimal system responsiveness. The recommendations below outline key measures to help safeguard your environment while ensuring Web Port runs efficiently and reliably.
Account Management
-
Enable password complexity – use strong passwords with uppercase, lowercase, numbers, and special characters.
-
Use personal accounts – never share login credentials between multiple users.
-
Protect your credentials – make sure they are not stored in a way that allows someone with access to your computer to use them.
Access Control
-
Limit administrator rights – only users who truly need admin privileges should have them.
-
Use groups and functional permissions – avoid global access levels when more granular permission control is possible.
Infrastructure and Network
-
Do not expose local networks to the internet – always use VPN for secure access. If VPN is not possible, use a node/portal.
-
Manage users in the portal – when using a node/portal, central user management in the portal is recommended instead of creating local users in the node.
Backup and Recovery
-
Configure backups of configuration values – ensure that all settings can be restored if needed.
-
Schedule periodic backups – in Windows environments, regular project backups are particularly important.
Identity and Authentication
-
Use Kiona Identity or Active Directory (AD) – for centralized and secure user identity management.
-
Enable Multi-Factor Authentication (MFA) – add an extra layer of security for user logins.
Performance Best Practices
-
Trend Interval – avoid setting trend intervals too frequently. The default interval is 600 seconds. Shorter intervals increase data storage and can quickly consume disk space.
-
Alarm Cycle – avoid configuring the alarm cycle too frequently. The default alarm cycle is 10 seconds. Shorter cycles generate more log entries, affecting both performance and storage.
-
File Logging – When logging to a file for troubleshooting purposes, avoid selecting a date far in the future to prevent unintended continuous logging if it is forgotten to be disabled. Use the default durations that is one hour, and only extend the logging period if necessary.
-
Audit Log – the audit log is enabled by default. To conserve disk space, consider disabling it if it is not required for compliance or monitoring purposes.
-
Metrics Log – the metrics log is disabled by default on new installations. On upgraded systems, previous settings are kept, which could mean that metrics logging remains active. If disk space is limited, metrics logging can be disabled.