DevOps Toronto
What we're about
The future of the software world lies in the co-operation of development, security, quality assurance, operations and any staff involved in value creation. Delivering top-notch products quickly requires automation, integration and collaboration.
This group is for people who share that vision. I wanted to create a meetup for like-minded folks to share ideas, complain, layout plans and vision for the future, and generally enjoy great company.
Join us on Slack! Click here to join our team and discuss DevOps and the Toronto tech scene between meetups.
Follow us on twitter - https://twitter.com/DevOpsTO
We'd love to hear you speak! If you have an idea for a talk you'd like to give or a panel discussion (with some suggested panelists you can help us wrangle) please post it here.
DevOpsTO loves partners! If you're interested in sponsoring the group, read more about it here.
Upcoming events (4+)
Agenda:
• 5:00 PM - Check in and hang out
• 5:05 PM - Lean Coffee Chat/Presentation
• 5:40 PM - Lean Coffee Chat/Q+A
• 5:55 PM - Wrap up, Next month
• 6:00 PM - Adios!
Many organizations claim to be all in on Observability, when in fact, they are not really following Observability practices. Over the last couple of years, I've observed a number of Observability anti-patterns, and in this talk, I'll be calling these out, in the hopes that senior leaders and individual contributors alike can avoid these, and be on their merry way towards unlocking Observability’s powers.
Join our Slack: https://vzbl.io/devopstoslack
If you'd like to be a speaker: https://bit.ly/speakatdevopsto
If you'd like to sponsor a meetup: steveelsewhere [ at ] gmail.com
- Steve P.
- Santos kumar M.
- Matt M.
- 99 attendees
Agenda:
• 5:00 PM - Check in and hang out
• 5:05 PM - Lean Coffee Chat/Presentation
• 5:40 PM - Lean Coffee Chat/Q+A
• 5:55 PM - Wrap up, Next month
• 6:00 PM - Adios!
Security is more than just checklists of common vulnerabilities and addressing questions from the security team. Development teams must add security to their full lifecycle view of product development. From product planning through development and testing to the operation of a system security should permeate each phase of product development.
During planning product teams need to perform threat modeling to evaluate what risks are present and how to prioritize them. Risks can be broken down and addressed iteratively, just like other product features. Adding security tests to the product framework will help the team to ensure that the product remains robust as features are added. Adding monitoring for security events will help the product team gain deeper insights into emergent risks.
These are a few ways that teams can practically address security in their products. Building a bridge for collaboration with the security team is another way. When a team is unsure of how to evaluate a given security risk, or if a threat model is accurate, they can reach out to their security team and ask for assistance.
When was the last time you’ve heard of a development team reaching out to the security team with questions, rather than the other way around?
Join our Slack: https://vzbl.io/devopstoslack
If you'd like to be a speaker: https://bit.ly/speakatdevopsto
If you'd like to sponsor a meetup: steveelsewhere [ at ] gmail.com
- Steve P.
- Matt M.
- Tim J.
- 7 attendees
Agenda:
• 5:00 PM - Check in and hang out
• 5:05 PM - Lean Coffee Chat/Presentation
• 5:40 PM - Lean Coffee Chat/Q+A
• 5:55 PM - Wrap up, Next month
• 6:00 PM - Adios!
Join our Slack: https://vzbl.io/devopstoslack
If you'd like to be a speaker: https://bit.ly/speakatdevopsto
If you'd like to sponsor a meetup: steveelsewhere [ at ] gmail.com
- Steve P.
- Matt M.
- 2 attendees
Past events (117)
- Steve P.
- ADAM
- Alexandr R.
- 78 attendees
