The Working Rubyist's Briefing on Designing for Security, Privacy, and Consent
Details
• Where We'll Be
This meetup, as with all talk nights this year, will be at the Ramsey Solutions Conference Center. Map to exact location with parking info: https://goo.gl/B1LWBZ
• What We'll Do
GDPR on Rails: The Working Rubyist's Briefing on Designing for Security, Privacy, and Consent
You’ve been hearing about big data breaches and CEOs of major Internet companies being called before Congress to testify about data privacy failures. As a Ruby developer who doesn't specialize in security, knowing how to protect your application from getting breached may seem like a daunting task. However, fundamentals in the design and development process will greatly increase the security that protects your users from harm. Additionally, for many American companies with users or clients in Europe, the deadline for compliance with the EU GDPR regulations is fast approaching on May 25, 2018.
Join us to learn about how security, privacy, and consent can become part of the design of your web applications to protect your customers and your company.
• Who Is Presenting?
Frank S. Rietta, MSIS
Web Application Security Architect
Rietta, Inc.
Frank Rietta is a web application security architect, author, and speaker. He is a computer scientist with a Masters in Information Security from the College of Computing at the Georgia Institute of Technology and founder of the Atlanta-based security firm Rietta Inc (https://rietta.com/).
Rietta Inc is in the business of defensive security. Our business is built around the realization that security cannot be bolted on at the end of a development process, and thus if you want to build web applications capable of withstanding constant attack, you have to build security into the development process itself. This has become even more critical with the rise of cloud-based computing and the proliferation of mobile applications that communicate constantly with publicly accessible web-based API servers to function. In our industry, the security perimeter is no longer defined as a network firewall, but is instead wherever your servers make an authorization decision. This means ultimately all security depends on software security.