Do you guys do any sort of software/hardware configuration hardening for new stuff?

Where I work we get a lot of requests for software and some of the software has a bunch of configuration options that could impact security if not configured a certain way or is just installed with the default settings.

Do you look at these types of things or create any kind of documentation on how it should be configured? We have a process for this now, but everyone is slammed with work and the current process really takes too long and ends up causing a headache for everyone involved because of how detailed some of these things have to be. I was hoping you guys might be able to give me some advice on how this could be better or more streamlined so it wasn’t such a big effort every time someone wanted to use a new tool they had at their last job that we’ve never seen before.

Touch here for the full post on Network Security Noblemen tumblr

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s