Understand the fundamentals
Management access can change production
A miner’s management interface is the web interface or tool used to view and change its settings. Changes made there affect how the miner works. Credentials, such as a username and password, prove who is logging in. That check is called authentication. Permissions decide what that person may do after logging in. That is called authorization. An API key or management token is a code that lets software log in without a person typing a password. Treat these, and any saved password, as secrets, even when the miner is on a private network.
Use only approved accounts and approved ways of connecting. Never make a management interface reachable directly from the public internet. Never show credentials in screenshots or tickets. A quick remote-access shortcut can cause a much bigger problem than the fault you were trying to fix.
Keep the management path separate from public services
Swipe sideways to follow the full diagram →
See how it works
Firmware and configuration have sources
Firmware is the software installed on the miner. A familiar model name in the file name is not proof that it came from the manufacturer. It is also not proof that it works with your exact model and hardware. The site needs approved sources, supported firmware files (called images) and a controlled change process. A promise of higher hashrate is never enough reason to install an unknown image.
A change to the pool endpoint, worker name, access settings or firmware can be approved maintenance. It can also be a sign of a problem. Check the approved record and the change history before you decide which. If you suspect a security problem, keep the evidence and escalate it. Do not change the settings back yourself unless the site’s process tells you to.
Connect it to the field
Example: preserve useful evidence without leaking secrets
If an unexpected pool endpoint appears, record the asset, the time, the firmware version shown and any settings that are not secret. Use the approved reporting channel. Do not copy passwords or tokens into the report. Follow the site’s incident process for next steps, such as limiting the damage (containment) and investigating further.
A good first response says what changed and who is authorized to investigate. Do not erase logs or factory-reset the machine to make the symptom go away, unless the responsible process tells you to. Doing so can destroy evidence and make recovery harder.
Terms used in this lesson
- Authentication
- Checks who or what is logging in, for example with a password.
- Authorization
- Decides what that person or program may do after logging in.
- Change record
- Records an approved change, who performed it and how the result was checked.
Optional references & further reading
Use current manufacturer instructions for the exact equipment and your site’s approved procedures. Course levels do not grant task authorization.