I can forgive someone who can’t explain how XSS or CSRF works (I’m not sure I can explain it so clearly myself—kudos to the article’s author for the excellent explanation) if they know about the top 10 and have read it at least once.
685 karma · joined January 25, 2017
I can forgive someone who can’t explain how XSS or CSRF works (I’m not sure I can explain it so clearly myself—kudos to the article’s author for the excellent explanation) if they know about the top 10 and have read it at least once.
If you have access to production logs and metrics, try to model things like page load times, server load, network latency, errors/timeout, number of page views/unique visitors.
You might hit on unexpected correlations and maybe unknown bugs (e.g. when page X is loaded with input Y, timeouts and server load increase because of a broken SQL request), or insights on the health of the production platform.
Note: it’s usually a good idea to let your own manager know of the situation and get their approval before attempting anything (to defuse any “going over the manager” gambit).
Anecdotally, I've been on the recruiting end of "anonimized" CVs pushed by outsourcing companies. I was never fully clear on whether this was a legal requirements for them, or if it was a gesture to show inclusiveness and social responsibility on their part (take this with a pinch of salt, most outsourcing companies in France are little better than horse-dealers and will push any warm body your way if they think they can turn a profit). At any rate, most of these were hilariously badly done: using initials for the last name but leaving the first name in full, leaving telling initials (1), or other subtle or less subtle ways to hint at the contractor's origin and gender.
(1) e.g. a first name initialed J.L., J.M. or some other variation points to a Jean-something (Jean-Louis, Jean-Michel, etc.) composite first name, which is a clear indication of a "native" Frenchman (and a hint as to the person's age as well)
Also, it’s helped me solve a few project Euler problems (which often involve framing “well-known” problems into novel forms). Brute-force the first few values and more often than not you’ll find the sequence in OEIS, sometimes with a generating function or pointers to the original problem.
Getting back to your example, there’s no “but” attached to choosing an existing engine, so you probably wouldn’t have a nagging thought pushing you to look at building your own.
So I guess what I’m really saying is “don’t cut corners”. You know you’re about to cut one when the little angel pops up on your shoulder and whispers “are you sure about this?”
Whenever you have to make a choice and there are an “easy” and a “hard” options, you should choose the hard option. It’s always the right one.
Why? If the easy option was also the right one, you wouldn’t even be thinking about it. The hard option is your conscience/instinct telling you to look beyond the obvious, easy answer.
The underlying reasons exposed by the book are timeless and universal. As I read the book (which, again, is 20 years old and focuses on the hard drive industry) I recognized all the pitfalls my previous company went through as it was trying to adapt to public Cloud.
This book is a powerful lens to look at disruptive innovation, well-written and very thoroughly researched. A must read if you’re working in technology IMO.
On the idea, I don't really see what differentiates you from the other million digital agencies and dev shops around the world. I like the tagline "rent a tech co-founder" but it doesn't really appear in your value offering.
And a "meta" question to finish: did you dogfood it? I.e. did you apply the methodology you sell and look for customers and talk to them? Did you build a MVP? (is this the MVP of mvpboost?)
At the very least, if you have N testers you can apply the technique pairwise to generate N(N - 1)/2 estimates for the number of bugs. Taking the average or median of these estimates would probably give you a more robust value for the total number of bugs.
You could also build a correlation matrix between testers (i.e. are bugs really independently found or do some testers tend to find the same bugs) and you could test the assumption that bugs are equally hard to find (which realistically isn't the case).
With that new insight into your original data, you could compute an a posteriori estimate for the total number of bugs, Bayes style.
(In other words, you start with the prior assumption that testers are independent and bugs are equally hard to find to build a first answer. Based on this estimate, you revise your assumption with a more realistic probability distribution for bugs and testers, and use that distribution to compute a new answer)
Or, maybe just stop messing with R and get on with fixing all the bugs found by your N testers.
* well, except for the very generic ones to not confuse what’s happening to you and your worth as an individual, to seek to learn or take away something good from the experience, and to remember that karma’s a bitch and that whoever screwed you will get their comeuppance one way or another.
I really feel for what happened to you, but I have trouble believing that a whole raft of incompetent VPs were hired just because they had BigCo du jour in their CV.
In other words, what would you have done differently to avoid this outcome, if you believe it was avoidable?
Companies do enforce security policies. Most often, there’s a bit of cargo culting / going through the motions to prove to compliance or the SEC or whoever that you’re doing something. It’s also complicated, on (large) companies’ timescales, to adapt to the changing threat models. Which is why we still have “8 characters including a number and an upper-case letter, to be changed every 3 months” nonsense instead of generalized password managers and MFA devices. (Try installing a password manager on your average locked-down corporate PC).
And even then, you’re still back to the fact that companies are large groups of people who range from Franck the IT guy who knows about security to Dennis from accounting who has all his passwords on a post-it and will gladly give them over the phone if “Gladys, the VP of marketing who needs access to the finance tool to update the budget forecast right away, before the big meeting with the CEO, you don’t want to upset the CEO do you Dennis” sounds persuasive enough.
However, I agree that companies are better at security than individuals, and will (hopefully) slowly drag the average security level up through employee education. It will take a while for the Dennises of the world to get the message, though.
People don’t care. They don’t even know that they should care. People have no clue how their PC or smartphone or internet access work. They don’t know what a hard drive is, they don’t know what encryption does, and their brain will explode if you try to explain what a MITM attack is. They just know that they had to return to the store last time they forgot their password so the geek with the “Apple Genius” T-shirt could reset it for them. So now it’s set to the kid’s birthdate. Because they don’t know how any of that stuff works, they have no choice but to trust the closest thing they have to an authority on the subject: their ISP, the guys who make their smartphone or their bank’s website, that salesperson at Best Buy who told them to install an antivirus.
Security is hard. Remembering passwords is complicated, picking good passwords is near impossible if you don’t have a tool to do it for you, and remembering those passwords is impossible. 2FA is a pain to set up even if ou know what you’re doing, and don’t even get me started on configuring “advanced” options (in which I bundle Fido2 / U2F for the foreseeable future). And recovery keys you’re supposed to print out and store in a safe, seriously?
Data is intangible. Contrary to a car theft or a house break-in, people struggle to assign a value to data loss or theft. Hell, I work in IT and I couldn’t begin to estimate the prejudice if someone were to gain access to my personal data. LoJacks and baby monitors help secure something that people can place a value on. What’s the value of my holiday pics?
Because of all this, security doesn’t sell. So companies have no incentive to invest in security, so security remains complicated and rare, so nobody gets to use good security and find out that it has a value, so security doesn’t sell.
I can’t even say that it will get better over time, as the young generations were raised to hand over control of their digital lives to corporate data harvesters.
Sorry for the bleakness of this post, but I’ve chosen to be jaded rather than depressed.
Step 1: hi TLO, what information do you have on me? Step 2: right, delete all of it.
Both have an abuse / phishing declaration form online. I signaled both pages, and they are still up for the moment.
Other factors: the bigger the company, the more inertia it has (assuming your job suppports its core business; even large companies will cut side or non-essential activities if the economic forecast is bad). B2B companies are less exposed to a recession at first, because of longer contracts and decision cycles in enterprise customers (it’s relatively easy and quick for an individual to downgrade their internet plan to save money; it takes much longer for a large company to renegotiate a telco contract). Defense is always a safe bet.
So basically the bigger the company, the more boring and/or morally dubious the sector, the better :D
Or, assuming the rest of the article is true, someone somewhere found out about the chip and had a quiet word with a few select customers of Supermicro (but decided to otherwise keep mum about the whole thing). Which would go some way to explain the company denials, because the truth might be a bit embarrassing —or gagged by a three-letter agency.