7.5 Test your backup strategy every now and then (nothing is more painful than data loss and dysfunctional backups)
8. "All users lie, there is no exception". Sad but true, get used to it.
9. Automate your infrastructure. If something goes down, just recreate it with Chef/Ansible/Terraform/etc.
[edit: added no.9]
11. Understand the reason the other guy was fired make sure you are not the one holding the bag.
12. Have a issue tracking system in place, you will thank yourself later.
13. Have a change management policy in place.
14. Before you make any change full understand the consequences and have a tested plan to get back to a known good state.
Dependant on what you have to look after you might want more than one book.
Maybe person X built system A, and is now working on system B, but remembers a lot of details - keeping their access to system A can help you recover in an emergency. Maybe someone wrote a monitoring job (or worse, a deployment job) that runs as themselves. Maybe someone has read-only access to a system and is using it to ask occasional good questions to the team that actually runs the system. Maybe team C has a formal API but it doesn't work well so person Y informally got access to C's database and it's making system D able to run at all, and it would take a few months of effort to fix the API that's supposed to be there between C and D.
And, more frustratingly but no less impactful - maybe there's a senior person who likes still having access to system E, and making them mad will cause political problems for you and impose burdens when you you try to make any other changes, which gets in the way of your ability to solve all the other problems that you need to solve.
Your priority in the short term is to keep the business running, not to improve things. Insider threats are real, but they are much rarer than all the other reasons your business could get in trouble. If you don't have a good understanding of your tech debt and why the tech debt exists and how quickly it can be paid off, focus on that first.
Keep a text file, or OneNote or whatever, open while working an incident. Don't overthink it, don't over-complicate it.
You need this to know if your web sites, servers and services are running, and to be emailed or contacted when not. I am used to Nagios. I understand there is a Nagios fork, Icinga, which I know little about. Some people use Graphite, which I also know little about.
You can also have it check for disks running out, high CPU loads, inodes running out, heavy I/O etc.
Also, you can email etc. alerts, or pay for a company like Amelia to monitor a dashboard and page/call people at night if a server is down, or to even do some simple scripted remediation attempts.
7. Eventually, in 5-7 years, become a consultant, either in a consultancy, or freelance.
1. Require not 1, but 2 people, for hire, right now. It will take a long time until it gets approved, HR does their thing, and you (or someone else) hire people to help you.
2. Document, as fast as you can, all of the assets in your environment. Don't waste time on looking for software. Plain text or spreadsheet will do for start.
3. Identify the most important assets (servers, network devices, etc) - and try to understand what are your priorities for each. For example, availability for your frontend servers. Confidentiality and integrity for your server storing PII. Based on this, you'll understand what are your biggest risks. Would it be a business disaster if your website is down for few hours? Likely not. What about if the PII is compromised and you get huge fines and be in the news? More likely.
4. Find out who has the access to the most important assets, and cut off anyone who doesn't really need it.
5. Establish some sort of monitoring for the most important assets.