#98 - The weakest link: why all software needs security?

Published: Dec. 16, 2021, 9:57 a.m.

During this episode we will go over common security breaches where the weakest service/software were exploited, why all components of a system should get their share of security evaluation, and why secure software design and coding are important for developers on all stacks.

\nGuests\n\nNotes\n

0:01 - Intro and welcoming.

\n

0:07 - Exciting security news: Log4j zero-day exploit meltdown.

\n

0:13 - Java Naming and Directory Interface (JNDI).

\n

0:16 - A brief introduction of security from your perspective?

\n

0:22 - What are the software/system aspects that are more critically in need for security?

\n

0:32 - The weakest links for system security: Physical security.

\n

0:42 - The weakest links for system security: Network security.

\n

0:49 - The weakest links for system security: Employees.

\n

0:59 - Stuxnet, where employees contribute to getting malware to the org.

\n

1:02 - Social engineering attack: FB & Google fraud attack.

\n

1:04 - Small satellite apps: FBI website hack, ~100k email sent from a legit fbi.org email address.

\n

1:35 - Secure coding principles for developers

\n

1:45 - Securing small systems (usually considered irrelevant systems)

\n

1:54 - How to secure frontend?

\n

2:00 - How to make sure employees/developers machines are secure?

\n

2:09 - How to manage secrets

\n

2:28 - Wrap up and Goodbye

\nLinks\nPrepared and Presented by\n