text
stringlengths
0
2.67k
[3356.32 --> 3363.88] the ships so i think there's some parts of um communities you know get a bad rap but you know
[3363.88 --> 3368.10] most of the ones that i've personally encountered have been fantastic so you know we were talking a
[3368.10 --> 3375.22] little about flutter earlier the flutter community is just lovely so far my encounters with uh open ssf
[3375.22 --> 3381.64] have been amazing so you know nice people doing good work so if someone wants to get involved where do
[3381.64 --> 3391.14] they start i would suggest you know start at uh open ssf.org then they can see scorecard as one of
[3391.14 --> 3395.84] the projects there and that'll take them into the scorecard mini site and that's kind of got a guide
[3395.84 --> 3401.66] on uh how to implement it whether you want to do sort of standalone with the command line tool or go to
[3401.66 --> 3407.52] the github action and make it an ongoing part of your repo how do you get involved with open ssf and
[3407.52 --> 3414.44] like the foundation because it sounds really cool so there's i suppose two different ways there so one
[3414.44 --> 3421.22] is formally becoming a member of open ssf and you know that works like so many of the other linux
[3421.22 --> 3426.80] foundation projects so it's a very organizational approach and if your organization's already a member
[3426.80 --> 3431.92] of linux foundation then you know there's a different price structure to if you're just going
[3431.92 --> 3437.00] in to join the open ssf that doesn't seem to be an individual membership approach at the moment
[3437.00 --> 3441.96] that brings me into the sort of second area of it doesn't really matter because it's a very open
[3441.96 --> 3449.36] and welcoming community so if you've got issues or prs or other ways of contributing the repos are there
[3449.36 --> 3455.74] and you can go along and do that they don't seem to be gatekeeping activities around open ssf to just
[3455.74 --> 3463.42] people who work for organizations that are open ssf members so i'm getting involved next week in a
[3463.42 --> 3471.08] webinar it's not next week after that um open ssf are doing about the topic of scorecard and it's a
[3471.08 --> 3477.64] combination of customers of scorecard like us and then some of the people who've you know created and
[3477.64 --> 3484.10] maintained it cool and if people want to reach out to you online where are you available so i can be
[3484.10 --> 3492.98] found at chris.swanswithaz.net and that's kind of got links to all of my social media and linkedin and
[3492.98 --> 3500.42] github and all that kind of stuff and so yeah i'm pretty easy to to then kind of you know find a route
[3500.42 --> 3506.34] through to and of course in amongst that i've done a few presentations about scorecard it's very much
[3506.34 --> 3512.44] focused on a practitioner's approach you know what does it take to build the foundations within
[3512.44 --> 3519.52] your organization to do your first repo and then to repeat that process across the other repos that
[3519.52 --> 3526.00] you want to put scorecards onto yeah i could see this at a large enterprise or company being very
[3526.00 --> 3530.04] political i could see you know like because there's a lot of security tools there's a lot of people
[3530.04 --> 3534.82] that want to focus on security and there's a lot of people that have strong opinions about
[3534.82 --> 3541.44] security implementations and i could see this as a starting point of if you don't have
[3541.44 --> 3546.68] good security practices like hey we should try this because it's open and it's free for us to
[3546.68 --> 3552.84] get started free is there's no buy-in to use the tool but not free as in it does take time
[3552.84 --> 3559.38] and being able to show off within your organization how that could work but also like maybe even pushing
[3559.38 --> 3564.18] back on some of the more closed vendors that don't provide anything like this of like we you trust our
[3564.18 --> 3570.02] tool to do all the scanning and we give you a green checkbox inside of our dashboard which isn't
[3570.02 --> 3576.58] publicly available or shareable and i've used plenty of security tools in the past uh that are are very
[3576.58 --> 3581.42] closed about and guarded about their secrets of how they score things and how you can improve those
[3581.42 --> 3586.46] things and not being able to share those things and so i could see this as being an open approach of
[3586.46 --> 3591.50] like this information should be available to more people and you shouldn't need a paid contract
[3591.50 --> 3598.94] uh to be able to verify if this works in your repo or with your your languages or not i work with a lot
[3598.94 --> 3603.64] of like college students and military spouses like learning how to code and kind of like learning how
[3603.64 --> 3608.80] to get into tech and i wonder if scorecards would be like a nice way to teach them about like securing
[3608.80 --> 3613.56] their github repos because i'm teaching like git classes but i also wonder if like are there any like
[3613.56 --> 3620.50] pathways for like college kids to get involved in like open ssf or like any other other open source
[3620.50 --> 3626.08] organizations that you're like oh there absolutely are and so there's so many projects and so much
[3626.08 --> 3632.60] work to be done and so yeah i'd encourage people to go and take a look there there's new stuff happening
[3632.60 --> 3639.66] on an almost daily basis and and of course an awful lot of toil behind it which needs you know many hands
[3639.66 --> 3646.54] to um to get to the work there the other thing this gets you to is when you're doing this in your own
[3646.54 --> 3652.20] repos and especially if you've got multiple ones as you're moving forward from that you want to have
[3652.20 --> 3658.52] good quality templates that just have everything done already but also you want to have repeatable
[3658.52 --> 3663.46] config or them you were saying earlier oh i want to get into terraform it's like that's your hook to
[3663.46 --> 3669.54] get into terraform because you can use terraform to have consistent good config across all of your
[3669.54 --> 3674.70] GitHub repo and that's the general rule for most like a lot of things start as toil we do them manually
[3674.70 --> 3678.28] we figure out the pattern and then we make a template from it and then we do the template over
[3678.28 --> 3681.96] and over again and then we automate the template and then we abstract the template right like that's
[3681.96 --> 3686.06] the the general like flow for anything in infrastructure and software it's just like hey
[3686.06 --> 3690.70] we figured out the hard way to do it we figured out an easier way that was repeatable and then we're
[3690.70 --> 3694.06] just like now we don't think about it anymore and at some point hopefully some of this stuff just
[3694.06 --> 3698.80] becomes abstracted away like hey this is just the defaults like if you don't do this it'd be
[3698.80 --> 3703.74] surprising right like that eight score is not something you have to achieve anymore if you drop below an
[3703.74 --> 3707.78] eight like you probably did something very wrong and we need to figure out how to get everyone to
[3707.78 --> 3714.40] that level eight of like best practices or just best practices and everything is defaulting to that
[3714.40 --> 3719.56] and so i think that's a really cool long-term safe defaults this is normal but it's also teaching you
[3719.56 --> 3724.64] best practices in the you know while you go through it so it's also like a great learning opportunity at
[3724.64 --> 3728.56] the same time so it's even better you know especially right now as it's changing that's what i'm saying
[3728.56 --> 3733.64] so much has happened in infrastructure in the last four years like it's wild how far we've come you know
[3733.64 --> 3740.12] like so getting better best practices and better ways to set up your next project i mean there's
[3740.12 --> 3745.42] definitely like a lot of value in that you know well chris thank you so much for coming on the show
[3745.42 --> 3751.42] today and talking to us about open ssf scorecards and uh hopefully anyone that's interested wants to
[3751.42 --> 3756.60] reach out to either you or open ssf they can get involved and and try out the tool go run it like i just
[3756.60 --> 3761.16] ran it during this podcast and it's super quick and showed me that you know i'm i don't have any
[3761.16 --> 3764.82] vulnerabilities in my bash but i could make some improvements still and that's kind of the goal
[3764.82 --> 3769.84] of being able to level up everyone on where they can improve for especially areas that like i didn't
[3769.84 --> 3775.66] realize you know maybe i need to do uh some more work in my repos so thanks chris for coming on and
[3775.66 --> 3778.70] uh we'll talk to you again soon thanks thanks chris
[3778.70 --> 3802.58] what's up friends this episode is brought to you by our friends at cinedia cinedia is helping teams
[3802.58 --> 3809.32] take nas to the next level via a global multi-cloud multi-geo and extensible service fully managed by
[3809.32 --> 3815.20] cinedia they take care of all the infrastructure management monitoring and maintenance for you so
[3815.20 --> 3820.72] you can focus on building exceptional distributed applications and i'm here with vp of product and
[3820.72 --> 3828.64] engineering byron ruth so byron in the nas versus kafka conversation i hear a couple different things
[3828.64 --> 3834.96] one i hear out there i hate kafka with a passion that's quoted by the way on hacker news i hear kafka
[3834.96 --> 3841.62] is dead long live kafka and then i hear kafka is the default but i hate it so what's the deal with
[3841.62 --> 3848.30] nats versus kafka yeah so kafka is an interesting one i've personally followed kafka for quite some time
[3848.30 --> 3854.64] ever since the linkedin days and i think what they've done in terms of transitioning the landscape to
[3854.64 --> 3860.66] event streaming has been wonderful i think they they definitely were the sort of first market for
[3860.66 --> 3866.18] persistent data streaming however over time as people have adopted it it was they were the first
[3866.18 --> 3871.98] to market they they provided a solution but you don't know what you don't know in terms of you need
[3871.98 --> 3878.32] this solution you need this capability but inevitably there's also all this operational pain and overhead that
[3878.32 --> 3885.60] people have come to associate with kafka deployments based on our experience and what users and customers
[3885.60 --> 3892.56] have come to us with they would say we are spending a ton of money on spend on a team to maintain our
[3892.56 --> 3900.58] kafka clusters or you know manage services or something like that the paradigm of how they model topics and
[3900.58 --> 3907.52] how you partition topics and how you scale them is not really in line with what they fundamentally want to do
[3907.52 --> 3912.64] and that's where nats can provide as we refer to it subject-based addressing which has a much more
[3912.64 --> 3919.46] granular way of addressing messages sending messages subscribing to messages and things like that
[3919.46 --> 3924.84] which is very different from from what kafka does and the second that we introduced persistence
[3924.84 --> 3931.86] with our jet stream subsystem as we refer to it a handful of years ago we literally had a flood of people
[3931.86 --> 3939.02] saying can i replace my kafka deployments with this nats jet stream alternative and we've been getting
[3939.02 --> 3946.30] constant inbounds constant customers asking hey can you enlighten us with what nats can do and oh by the
[3946.30 --> 3951.86] way here's all these other dependencies like redis and and other things and some of our services based
[3951.86 --> 3957.66] things that we could potentially migrate and evolve over time by adopting nats as a technology as a
[3957.66 --> 3964.00] core technology to people's systems and platforms so this has been largely organic we never from day