{"id":603,"date":"2009-06-26T17:27:24","date_gmt":"2009-06-26T07:27:24","guid":{"rendered":"http:\/\/nsrd.wordpress.com\/?p=603"},"modified":"2009-06-26T17:27:24","modified_gmt":"2009-06-26T07:27:24","slug":"your-datazone-is-only-as-secure-as-your-networker-server","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2009\/06\/26\/your-datazone-is-only-as-secure-as-your-networker-server\/","title":{"rendered":"Your datazone is only as secure as your NetWorker server"},"content":{"rendered":"

A topic I discuss in my book<\/a> that’s worth touching on here is that of datazone security.<\/p>\n

Backup is one of those enterprise components that touches on a vast amount of infrastructure; so much so that it’s usually one of those most broadest reaching pieces of software within an environment. As such, the temptation is always there to make it “as easy as possible” to configure. Unfortunately this sometimes leads to making it too easy<\/em> to configure. By too easy<\/em>, I mean insecure<\/em>.<\/p>\n

Regardless of the “hassle” that it creates, a backup server must<\/em> be highly secured. Or to be perhaps even blunter \u2013 the entire security of everything backed up by your backup server depends on the security of your backup server<\/em>. Having an insecure NetWorker server, on the other hand, is like handing over the keys to your datacentre, as well as having the administrator\/root password for every server stuck to each machine.<\/p>\n

Thinking of it that way, do you really want the administrator list on your backup server to include say, any of the following?<\/p>\n