Application security

How to use authorization in Laravel: Gates, policies, roles and permissions

Learn how to use Laravel in authorization to your application.

Is your company testing security often enough?

Is your company testing security often enough?

Security is an ongoing process: you’ll need to regularly reassess your system for vulnerabilities.

Authentication vs. authorization: Which one should you use, and when?

Take a look at the difference between authentication and authorization and what works best for you.

Why your company should prioritize security vulnerabilities by severity

Why your company should prioritize security vulnerabilities by severity

You want a system in place to grade severity so you know where to focus your efforts, and in what order.

There’s no such thing as “done” with application security

There’s no such thing as “done” with application security

Technology evolves so quickly that it requires you to constantly revisit your security to stay ahead of new vulnerabilities.

Understanding hackers: The insider threat

Understanding hackers: The insider threat

Companies often think of attackers as something that comes from the outside, yet overlook the far more dangerous threat: attackers from within.

Understanding hackers: The 5 primary types of external attackers

Understanding hackers: The 5 primary types of external attackers

In order to defend, it’s important to understand who the attacker is and what motivates them.

Want to improve the security of your application? Think like a hacker

Want to improve the security of your application? Think like a hacker

Explore the assumptions you’ve made about your application, and try to get the system to respond in ways it isn’t supposed to.

5 problems with securing applications

5 problems with securing applications

For many companies, getting started on securing their application is riddled with logistical and practical challenges.

Why you should build security into your system, rather than bolt it on

Why you should build security into your system, rather than bolt it on

When you postpone security until later in the software development process, that delay costs you enormously in obvious and unexpected ways.