network_defender ✭✭✭✭✭

but who is going to fact check snopes

Sneak it in with lunch and out with the trash.

Had to read and reread today's (Friday) question. Got it right. 15 for 15. Anther T-shirt to add to the collection.

I agree with the programming knowledge helping in the troubleshooting arena. Back in the mainframe days, a knowledge of programming was a requirement to troubleshoot.

Always searching for a deeper understanding, regardless of complexity.

That sounds much more efficient.

Reminds me of my General Radiotelephone Operator License from 1995.

This has been slowly coming along far a couple of years now. The ideas became plans and those plans are being implemented. I have adopted a wait and see attitude before I develop an opinion. From where I sit, there seems to be less local control and monitoring. We will see. Just like anything in DoD IT, we move forward…

Chewbacca all the way!!

As an old school main framer, I miss magnetic core RAM and a CPU that was spread across several circuit cards.

Oh good grief. If you can't handle the interview, what are you going to do when VCenter goes down?

Nobody is looking at the logs?

This person doesn't understand the value of letting others know what eh\she has done?

Keep us informed. We are looking from McAfee to Cisco.

Tenable. It is part of the ACAS system the DoD is now using. Quite satisfied.

Well written. The challenges are many and personnel are sparse. It will be interesting to see this develop. 

The reading for Thursday's question was less than clear. Is it possible to get a reset?

Good read. I totally agree.

Trust but verify.

Just view it as a continual chess match. Constantly thinking several moves ahead. One of my coworkers and I will often have verbal chess matches playing a version of red team, blue team. He will take offense, such as an insider threat, and I will take defense. We verbally spar, challenging each other's knowledge attack…

Agreed!

Yes. We have two separate Dev networks. Play and learn all day without breaking the production network.

Smiling and shaking my head.

I agree with day 8. However, day 7 question said "increase database capacity", but the answer was "estimate database capacity".

I'm not sold on the self driving technology technology, but the technology is interesting to read about.

Couldn't agree more. We need to see the grass through the weeds.

The Security and Compliance Tango. Be fluid, but stay sharp. Security requirements tend to change much more quickly than compliance requirements. Oddly enough, I actually had this argument with an IA manager I once worked for. He insisted that if we were compliant, we were secure. He isn't in security anymore.

Does the desire for convenience out weigh the need for security? It all comes back to the CIA triad. Confidentiality, Integrity, and Availability. Is the desire for Availability greater than the need for Confidentiality and Integrity? How much freedom are you willing to give up for security? These are difficult questions,…

Great write up. We've all been there, troubleshooting a connectivity problem that just "clears up".

All that is needed is a smoke reinsertion device, provided you have the right smoke.