While the networks Reputation system, which is used for job allocation, incentivizes creators and node operators to act in good faith, there are also additional technical processes to reduce malicious behavior on the network. To prevent spamming attacks, like submitting thousands of jobs at only a few samples, the network will not let a user submit a new job without first paying for prior work or having enough tokens in their account to pay for the work. As a result, such an attack would be extremely wasteful. When malicious or bot-like activity - like rapid job generation - is detected, a user or node will be quarantined. On the node operator side, the RNDR client uses a heartbeat to ensure that a node is online and to prevent crashes. If a return signal is not detected the client is restarted. This process helps ensure reliable uptime.
RNDR also has log files from the RNDR client that generates forensic data to be used for security. A system tray application is the RNDR software itself. If someone manages to steal and reverse-engineer the systray app, at its core it is a wrapper that can connect to an external system. The Octane software is well protected, because the node client doesn’t hold Octane itself, but allows the node to run stripped down parts of Octane that are needed ‘on the fly’.
Finally, RNDR client software goes through periodic automatic pull-downs of new versions in order to minimize exposure to malicious behavior from older clients. Finally, all assets are fully encrypted end-to-end and at rest, reducing hardware vulnerability.