OP here. I'm very interested in two things: thinking about new types of security tools and studying how different systems, especially those that are not computer related, are secured.
This repo is for people who also fall into the second camp and are curious about how prisons are secured, how museums are secured, etc. And the techniques used to do this systematically -- kill chains, failure analysis, and so on.
Happy to hear your feedback, and sorry if it's a bit disorganized!
What's unfortunate is that a lot of bills are not even brought up in the Senate or the House for a vote after the other house passes them, often with overwhelming bipartisan support.
This effectively grants the Senate majority leader and House speaker veto power over any legislation. Even if the rest of the body supports the bill, the leader of the house can just kill it by refusing to bring it up for a vote.
I'm not sure whether this practice happens because the leader of the bodies don't want it to pass, or there's not enough floor time to bring it up, or if these bills are ultimately tucked into an omnibus package and passed into law that way.
The good news is that if people and their legislators truly care about this issue, they can demand that leaders allow votes as a condition for their support. The system is bad right now, but it can be changed.
Why would they? If your state senator is a high ranking representative like the Senate Majority Leader, you like that your state has more power.
Because of the way the Senate is structured with two representatives per state regardless of the population, that gives the less populous flyover states and the “Bible Belt” way more power than their population would entitle they to.
If QI was a law, the supremacy clause would certainly apply.
But QI is not a law, however it is a policy created by the courts based on federal law. It’s not clear to me whether the supremacy clause applies here, but I suspect it does.
Author here; let me know if you have any questions.
This repo is a work in progress. I think it has enough content to be useful to others, so I thought I'd share it. But I hope to continue to study security engineering throughout my lifetime, so it hopefully be a work in progress forever :)
Anyways, this means I would very much appreciate any pull requests or issues with links to new books and papers to check out on this topic!
I'm very interested in learning how to secure anything. What we're securing may be computer-related, but it might be a painting in an art museum or a medieval castle or a ATM machine...is there a set of steps I can follow to secure it?
That's why I created this repo. I've included links to many different books and papers in this repo, as well as notes on any books and papers I've read.
This will hopefully be a lifelong curiosity for me, so if you have any other resources I should look at, please submit a pull request and I'll merge it in. The repo is very much a work in progress; I by no means have read everything that I've linked to. Let's make this a collaborative effort!
https://colab.research.google.com/drive/1Y65qXXogoDgOnXFBDyF...