 Time here for more on systems and we're going to talk about securing your true NAS core installation now I did say specifically true NAS core and most of these will generally speaking apply to true NAS scale But as of January 2022 true NAS scale has not been fully released in the future once it is released You can check my channel if you're watching it in that future There's probably going to be a video on that topic and more specific the true NAS scale But today we want to cover some general good security practices for configuring your true NAS core system And let's get started with that But first if you like to learn more about me and my company have a little Lawrence systems calm You like to hire sure a project such as storage consulting There's a hires button right at the top if you want to support this channel other ways There's affiliate links down below to get your deals and discounts on products and services We talk about on this channel and the first thing worth mentioning is multi-factor authentication Let's just get that one right off the top. It's easy to do in true NAS, but I want to make sure you're doing it properly There's a little bit of a problem So to speak that you can create for yourself if you're setting this up when you enable it and you create the secret and you click On enable which right now says disable two-factor where you can go ahead and click disable see what it looks like We're gonna go ahead and caution once the two factors enabled The one-time password will be required to sign in a system. Be sure you immediately set up another two-factor device confirm Please note it did this without asking me if I actually clicked on that show QR code or displayed the secret I highly recommend you make sure and when you set this up and hit enable open up Maybe an incognito window or a different browser try to log in make sure it works and that's really important This is one thing that were people have found themselves in a little bit of a Problem where you turn on two-factor which I highly recommend doing but you also end up not realizing that Oh, I didn't copy the QR code or I didn't do that I just hit enable and then I logged out and log back in but I forgot to show QR or reveal the secret So you can copy it into your app. So FYI and that second thing of note, please note I have the window set to one This is a specific feature here the window to extend the validity of passwords beyond the interval setting Basically having one means the one before and the one after will work The reason I did this is I recommend doing it if you are worried at all about the system ever getting out of sync If you do have NTP servers in there, it shouldn't be an issue But if these codes that roll every 30 seconds on interval and you have a machine more than 30 seconds out of sync When it comes to time you will find yourself unable to log in now I don't exactly know how often this happens but it's happened a couple times where the system seemed to wander just a little bit out of time and Never more than just a few seconds out of time. So this solved it for me Hopefully that helps someone out who's had trouble with the 2FA. I've seen some posts and forums about that Next thing that seems obvious and it's a good practice in general is making sure everything is on the latest version TrueDAS core is at 12.0 u7 as of right now in January of 2022 beginning of January. So just make sure it's up to date This solves not just feature problems But sometimes solve security problems because as they update the modules if there's a flaw in something such as SMB for an example You will find that that's part of the update is to fix any of those flaws in the different components that make up your TrueDAS system Next thing is all about the admin interface I just want to bring this up that making sure that you lock down the admin interface is one of the utmost important features of TrueDAS And I'll touch on it more when I get to the part about snapshots But essentially you need to keep people from getting in here more than anything else now if and ideally you should have a system set Up with multiple network interfaces and then you can have one of those interfaces dedicated to being management Now if you're a home user, this is probably less of an issue But I've talked a lot on a channel about segmenting networks and the more you segment your networks the better overall security you will have by creating these rules and isolating different segments of network to not allow what they referred to as lateral movement And that's what a lot of these next steps are going to be about network segmentation and interface segmentation Instead of creating firewall rules, which isn't really a option through the UI here in FreeNAS slash TrueNAS because this has been this way for quite a while The system has where you bind it to the IP addresses you want So this right here is the VLAN I do not think ever needs to access the admin interface these two I do want access to the admin interface So you just check these on and off as needed and this is what allows the Interface to be bound to those addresses. That means they're accessible from those networks I do recommend making sure you have the web interface HTTP HHS redirect turned on and after that just save the config and you're good to go next on the network segmentation list It's going to go over to the services First is always really simple. Which services do you need on? Are you using those? I hope you're not using FTP even though it is still available here inside of TrueNAS But if you don't need a service you turn it off if it's not in use Disable it until you need it and this really goes down for any of these services secondary is Bind these services only to the network interfaces that they're used on really This is simple to do if we have like the SMB protocol. We can go here We go into an advanced and right here is the IP addresses that we can bind it to I don't care for it on this network I need it on this network here. This is where a few things need to connect via SMB It's perfectly fine to have the admin interface somewhere else But only allow the samba shares to be right here same thing if we went over to like NFS F Or S3 any one of these you just bind it to the interfaces where it's relevant And that just helps eliminate any potential issues from being exposed on networks Where it's not needed to go a step further some services such as iSCSI or NFS both support Narrowing the scope of what can even connect to them based on IP addresses that way when you're doing any the sharing You're limiting it in scope even further So the more you can limit in scope and practice these principles of least privilege the safer everything is Specifically, let's talk about SSH though where I highly recommend only having SSH with the keyed Authentication this checkbox here allows a interactive or password based off I highly recommend limiting it to key authorization So if you do need SSH on for whatever reasons or maybe you're doing some replication and connecting over it to send things That's fine But you want to do it all with key management and I've got videos on SSH and key management let's move on to the jails and the jail system here the Jails are not something I use a lot So I set these two jail demos up and I have an entire video because it's out of scope to talk about some of the Intricacies of setting this up, but yes jails can be tied to different VLANs So this jails tied to the one seven two sixteen sixty nine Slash zero slash twenty four VLAN too, but I want the jail on that interface So it can then talk to that network This is ideal for situations where let's say you have a media streaming service or tools such as Plex And you want Plex to be in the IOT network with the other devices so it can streaming cast directly to them But you don't want maybe your Samba shares or your admin interface in that network Or maybe you take from your computer and share the data You can have that bound to the SMB and then your jails will expose data only inside of Plex over to that media streaming network Without other things being tied to it and you can set this up on a per jail basis I'll leave a link to the video I have or I talk about jails different networking and different VLANs and setting that up and Configuring it, but it's another one of those best practice type things is having each Thing in the network that it's going to be interacting with the other devices You can obviously route some things for your firewall to create different restrictions But this obviously creates some challenges where you're routing a lot of extra things through your firewall Creating different rules putting a burden on a firewall to try and expect that traffic or in the case of some of the streaming devices they expect the same subnet to be the Device and where the streaming is coming from, but that's just a way to configure it here to solve some of those problems Now let's briefly touch on physical security. We're gonna go here to storage. We're going to the pools When you're setting up the pools, hopefully you created it with keys I highly recommend doing this that way if ever a hard drive where to go bad You can confidently remove it from the pool and because the keys are stored on the boot drive There's no key information and your information is completely encrypted on that drive So there's one level of security The next level of security is what if someone physically took your whole TrueNAS system? Well, this would be obviously very problematic And one of the ways you can help mitigate risk is if you have any particular data set that you've created You can go to that particular data set go to encryption options and instead of inheriting a standard key encryption You can go passphrase on this now. This creates the inconvenience of every time you reboot your TrueNAS system of having to type in a passphrase to unlock that data set But creates the security that if somewhere to physically take your entire server and figure out a way to start it up and get into it and Acquire those keys off the boot drive that they still wouldn't have this tight-end password We do this for any of our critical stuff It as I said creates the inconvenience of rebooting means I have to also unlock those particular data sets But creates that security of well without those passwords and without putting those passwords in that data set is completely locked The next piece of physical security is going to come under system and then advanced Show text console without password prompt You can uncheck this if you're familiar with the way the text console works It allows you to type in and be able to control some functions and even reset the web password right from the Command prompt on the system. This is one of those things that well Maybe you don't want on there because you're worried a little bit more about the physical You can just check this box and then removes that you'll have to have the Root and password in order to type in interactively and hopefully you have a good password and that wouldn't be easy to do now The last component I want to talk about is snapshots. I've talked about them a lot on this channel Snapshots are with CFS specifically a block level snapshot Instance of your data at the moment you took the snapshot They're an excellent way to protect the data They are only manageable through the command line interface via SSH or directly on the system or via the web interface That's why all the four mentioned things are so important to keep people out of those because the question comes up What if we have a window share? What if we have this system tied to active directory? And we have a user who clicks on something with a high level of privilege and they destroy all the files and Crypto all the files do something terrible to them well snapshots roll it back But then the next question of how do you make those immutable? How do we make sure no one from the windows connection gets in there and the way it works inside of true nas the Windows systems do not have access to the snapshots from a read-write perspective There is the option to turn on and I've done video about this volume shadow copies emulated through true nas So snapshots appear like a shadow copy, but unlike a shadow copy. They're emulated through SMB and They're actually ZFS snapshots and they're all read only so technically from the windows perspective It is immutable anytime you've seen major losses from someone who had snapshots set up And maybe got ransomware or something happened to all their data. You'll find that they probably had Access to the admin interface with a shared password to something else where somehow the threat actors or whoever had the idea to Do something terrible to the system also had access to that admin interface and got onto the true nas if they only have it Exposed through ice cuz the NFS s3 insert name of all the different methodologies for connecting data to true nas They do not have direct access to the snapshot library or a snapshot file system Essentially, that's created with ZFS where all that snapshot data lives and is controlled and is managed So as long as you keep the admin interfaces locked down and no one gets in them the Encryption of all those files is still protected with snapshots because you can just revert back to the previous snapshot Now how frequently and how long should you keep those snapshots is still going to be on your storage needs and what you Can find reasonable based on how much storage you have how much data is have and I've leave links down below to where I dive A little bit more in depth on a snapshot topic So hopefully this gets you started and secured with true nas if you have some questions comments and concerns leave them down Below if you want to have a more in-depth discussion about this video head over to our forums All right, and thanks and thank you for making it all the way to the end of this video If you've enjoyed the content, please give us a thumbs up if you would like to see more content from this channel Hit the subscribe button and the bell icon If you'd like to hire a short project head over to LawrenceSystems.com and click the hires button right at the top to help this channel out in other ways There's a join button here for YouTube and a patreon page where your support is greatly appreciated For deals discounts and offers check out our affiliate links in the description of all our videos Including a link to our shirt store where we have a wide variety of shirts that we sell and designs come out Well randomly so check back frequently and finally our forums Forums.laurancesystems.com is where you can have a more in-depth discussion about this video and other tech topics covered on this channel Thanks again for watching and look forward to hearing from you