In the first post in this series, I wrote about the fact that security is not a one-time task. It must be part of your whole development process. This week I want to share some thoughts about security in requirements analysis.
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
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
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: Client XSS Server XSS Both of these can be either
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
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
I hope that you already know that users hate meaningless error messages. (Actually they hate all error messages – don’t we all!) So that’s one reason to not allow default messages to display in your web application. But there is another important reason: security!
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.
Stay home. Stay safe. Stay informed. Find information at www.sacoronavirus.co.za
Thank you for completing the form. We're excited that you have chosen to contact us about training. We will process the information as soon as we can, and we will do our best to contact you within 1 working day. (Please note that our offices are closed over weekends and public holidays.)
Our privacy policy ensures your data is safe: Incus Data does not sell or otherwise distribute email addresses. We will not divulge your personal information to anyone unless specifically authorised by you.
If you need any further information, please contact us on tel: (27) 12-666-2020 or email info@incusdata.com