TL;DR / Summary: A family NAS holds photos, documents, and backups, and usually runs on one shared password that nobody changes. Give each person their own account, rotate the admin credential on a schedule, and keep the rotation somewhere the household can find it.
The shared-password problem
A NAS with one account for the whole household is easy to set up and impossible to audit. When someone leaves the household, or a device is lost, there is no way to revoke access without disrupting everyone.
Per-person accounts solve this. Each person has their own credentials, their own permissions, and their own devices authorised.
The administrative account should be separate from the everyday accounts and used only for configuration. Browsing the family photos as an administrator is a habit that turns a routine login into a privileged one.
What to rotate, and how often
Not every credential needs the same schedule. Rotating everything monthly creates fatigue and leads to a sticky note on the router.
- Admin account — rotate annually, and immediately after any staff change
- User accounts — rotate on compromise or device loss, not on a calendar
- Service accounts — rotate when a device is replaced
- Wi-Fi credentials — rotate when a device leaves the household
The logic is risk-based. The admin credential is powerful and rarely used, so an annual rotation is manageable. User credentials are used daily, and forced rotation produces weak passwords.
A rotation that does not break everything
Before rotating, list every device and application that uses the credential. A NAS credential is often stored in phone apps, desktop sync clients, and media players.
Rotate, then update each device immediately. A rotation that leaves three devices broken is a rotation that will be reversed.
Rotate the admin password on a schedule. Rotate user passwords on events.
Storage of the household credential
A single household password needs to be available to everyone who legitimately needs it, which conflicts with good password practice.
A password manager with a shared vault solves this. Each person has their own master password, and the shared vault holds the household credentials.
Where that is too much infrastructure, a sealed envelope in a known place is better than a note on the fridge. It is not elegant, and it is a reasonable compromise for a family network.
Account hygiene on the NAS
Disable or delete accounts for people who no longer need access. An account that has not been used in a year is a liability, not a convenience.
Review the account list twice a year. It is a five-minute task that catches forgotten guests and old devices.
Check the login history if the NAS provides one. Repeated failed logins from an external address are worth investigating, and most NAS devices log them.
Exposure to the internet
A NAS exposed directly to the internet is a target. Automatic scanning finds these devices within hours, and NAS software has a long history of vulnerabilities.
Prefer access through a VPN rather than port forwarding. If remote access is required, use the manufacturer’s relay service with two-factor authentication enabled.
Disable any UPnP setting that opens ports automatically. It is convenient and it exposes services you did not intend to publish.
Backups are separate from credentials
A NAS is often the backup destination for household devices, which makes it a single point of failure. A NAS is not a backup unless its contents are also backed up elsewhere.
Follow the rule of three: the original, a local copy, and an off-site copy. For a family, the off-site copy can be an encrypted cloud backup or a drive at a relative’s house.
Test a restore once a year. A backup that has never been restored is a file, not a recovery plan.
A simple household policy
One admin account, one account per person, a shared vault for household credentials, remote access only through VPN or the manufacturer’s relay with two-factor, and an annual review.
For generating the credentials themselves, random password generator produces values that are genuinely hard to guess, which matters more than length alone.
A family NAS is a small piece of infrastructure with real consequences if it fails. A modest amount of hygiene keeps it useful for a decade.
Backups, snapshots, and the recovery drill
A NAS usually offers snapshots, which protect against accidental deletion and ransomware in a way that a plain backup does not. Enable them if the device supports the feature.
Snapshots are not a substitute for an off-site copy. A snapshot lives on the same disks, so a hardware failure takes both the data and the snapshots with it.
Run a recovery drill once a year: restore a folder from the off-site copy to a spare location and confirm the files open. A restore that has never been tested is a plan, not a capability.
A one-page household runbook
Write down the admin account name, where the shared vault lives, what the off-site copy covers, and who to call if the device fails. One page, stored with the household documents.
Include the device’s model and the firmware version. When something breaks in three years, that detail saves an hour of searching for the receipt.
Review the page when anyone moves out or a device is replaced. A runbook that describes a household that no longer exists is worse than none, because it is confidently wrong.