As access to AI models has become more widely available and more and more people are using these tools on a regular basis, many organizations are interested in providing AI tools to their employees and customers. A key problem with the publicly available APIs is that they have varying levels of security and privacy that donโt always meet the needs …
In the latest episode of Next Level, Zach has the pleasure of chatting with Tom Hill, Engineering Director at Corsearch, about his career journey and insights into tech leadership. Key takeaways for this week’s episode include… Non-Linear Career Paths: Tom shares his non-traditional journey into tech, starting as a creative and transitioning through various roles, including graphic design and UX/UI …
Developing custom applications is one of the hardest professional endeavors, and making them secure is even harder. Malicious actors are constantly changing tactics and strategies, which, unfortunately, makes it impossible to completely eliminate any security threat.
There needs to be a balance between delivering features quickly to meet business objectives and mitigating security risks. Thankfully, these two goals are not mutually exclusive. This blog post dives into the top mistakes that can be made while developing custom applications.
These recommendations are different from what would commonly be seen in an OWASP list, and they should be used in addition to whatever security practices and procedures are already in place by an organizationโs infosec department. These recommendations are also written from an application architectโs (rather than an enterprise infrastructure) perspective, so most of them arenโt covered by existing security checklists.