Quotes About Security

Then she stepped through security. She never came back.

He who is united to Christ and lives within the circle of his love, to him the eternal retention of the supreme eschatological life is absolutely secure.

At least he didn't have a gun." You know your day sucks when the high point is you haven't had a gun pointed at you.

Just in case you get any ideas, know that I'll be sleeping with a can of Mace in one hand and pepper spray in the other." - Katie Jorlan's expression turned mocking. "Just in case you get any ideas, know that I'll be sleeping with a feather in one hand and massage oil in the other.

There is only one thing you need to know about me," he finally said. "I will protect you as long as you are necessary, and as long as you do not seek my downfall." - Knox

The only thing more dangerous than a developer is a developer conspiring with Security.

we're hearing more lately: something called "DevOps." Maybe everyone attending this party is a form of DevOps, but I suspect it's something much more than that. It's Product Management, Development, IT Operations, and even Information Security all working together and supporting one another.

You get what you design for. Chester, your peer in Development, is spending all his cycles on features, instead of stability, security, scalability, manageability, operability, continuity, and all those other beautiful 'itties.

So much about DevOps is counter intuitive, contrary to common practice, and even controversial. If production deployments are problematic, how on earth can deploying more frequently be a good idea? How can reducing the number of controls actually increase the security of our applications and environments? And can technology really learn anything from manufacturing?

Imagine a world where product owners, Development, QA, IT Operations, and Infosec work together, not only to help each other, but also to ensure that the overall organization succeeds. By working toward a common goal, they enable the fast flow of planned work into production (e.g., performing tens, hundreds, or even thousands of code deploys per day), while achieving world-class stability, reliability, availability, and security.

I've also come across otherwise smart [people] who are of the mistaken belief that if they hold on to a task, something only they know how to do, it'll ensure job security. These people are knowledge Hoarders. This doesn't work. Everyone is replaceable. No matter how talented they are. Sure it may take longer at first to find out how to do that special task, but it will happen without them.

Frequently, Development will take responsibility for responding to changes in the market, deploying features and changes into production as quickly as possible. IT Operations will take responsibility for providing customers with IT service that is stable, reliable, and secure, making it difficult or even impossible for anyone to introduce production changes that could jeopardize production. Configured this way, Development and IT Operations have diametrically opposed goals and incentives.

In the technology value stream, we optimize for downstream work centers by designing for operations, where operational non-functional requirements (e.g., architecture, performance, stability, testability, configurability, and security) are prioritized as highly as user features.

The vendor assured us that it's safe, and we checked all their references.

two of the three legs of the 'confidentiality, integrity, and availability triangle' or cia." He

Situations like this only reinforce my deep suspicion of developers: They're often carelessly breaking things and then disappearing, leaving Operations to clean up the mess. The only thing more dangerous than a developer is a developer conspiring with Security. The two working together gives us means, motive, and opportunity.

The only thing more dangerous than a developer is a developer conspiring with Security. The two working together gives us means, motive, and opportunity.

Next, we found numerous instances where developers have administrative access to production applications and databases. This violates the required segregation of duty required to prevent risk for fraud.

Gatekeeper, the Facebook feature toggling service.

By adding the expertise of QA, IT Operations, and Infosec into delivery teams and automated self-service tools and platforms, teams are able to use that expertise in their daily work without being dependent on other teams.

A developer jamming in an urgent change so he could go on vacation—possibly as part of some urgent project being driven by John Pesche, our Chief Information Security Officer. Situations like this only reinforce my deep suspicion of developers: They're often carelessly breaking things and then disappearing, leaving Operations to clean up the mess.

Information Security is always flashing their badges at people and making urgent demands, regardless of the consequences to the rest of the organization, which is why we don't invite them to many meetings. The best way to make sure something doesn't get done is to have them in the room.

Information Security is always flashing their badges at people and making urgent demands, regardless of the consequences to the rest of the organization, which is why we don't invite them to many meetings.

Safety is a precondition of work.