According to the UK IT Governance blog, 148 million records were breached in December 2020!
As stories of data breaches hit the news each day, many companies are trying to patch the security of their systems as quickly as possible.
That’s a start, but it’s not enough. Security is not a one-time task. It has to be built into your development process, not added on as an after-thought.
There’s a reason you pay for plastic shopping bags. It is to protect the environment. Durable shopping bags can be re-used, and don’t pollute our oceans and landfills.
Re-use is a good thing – and not just for the environment. We know that code re-use is important. And that also applies to data. If we have data that is used in many places, we only want to store it in one place and have one source.
That’s the same principle behind XML external entities (XEE). Unfortunately, there’s a potential security loop hole.
Cross-site request forgery (CSRF or XSRF) is also known as “Sea Surf” or “Session Riding”. But unlike real surfing, it’s got nothing to do with waves, water or the beach.
Last week I wrote about Cross-Site Scripting, and the serious consequences it can have.
According to OWASP, XSS affects about two thirds of all applications. That statistic should scare you!
Now that I have your attention, let’s look at how we can stop XSS.
I’ve mentioned Cross-Site Scripting, aka XSS, in some of my previous posts. And I’m sure you’ve heard of it as well.
XSS is often categorised as either reflected XSS or stored XSS. And then DOM-based XSS was added. OWASP now categorises XSS as:
Both of these can be either reflected or stored, which can make it all a little confusing.
No, we are not talking about delicious double-chocolate cookies. Although I’ve really missed the fabulous Incus Data cookies during lockdown.
As you know, cookies are small text files. They are usually created by the web server, but are saved and managed by your browser.
Cookies can be harmless or incredibly dangerous. It all depends on how you use them.
I believe in code re-use. You believe in code re-use. No-one wants to re-invent the wheel, especially not if there is a really great, aero-dynamic, ultra-fast wheel available.
That’s why we use libraries and components. But those libraries and components are not written by super-humans. They are written by people like you and me – people who make mistakes.
I mentioned before that I am writing an online course on ethics for software engineers (which is now open for pre-enrolment!) During my research for this course, I found an interesting – and scary – statistic.
In a previous post, I told you about the importance of using HTTPS instead of HTTP. Today I will look at some of the functionality that HTTPS adds in the form of security headers.