Is Programming Necessary to be a Successful Hacker?

Discussions
15 Oct 202014:22

Summary

TLDRこのビデオスクリプトでは、セキュリティ分野でプログラミングが必要なかどうかについて議論しています。プログラミングはセキュリティの特定の分野では必要ない場合もありますが、プログラミングを知らないことは自分自身を不利な立場に置くことになるという意見が示されています。特に、セキュリティのスキルを向上させるためには、プログラミングの知識は非常に役立ちだと述べています。また、セキュリティの様々な側面でプログラミングがどのように役立つかについて、具体的な例を挙げて説明しています。最後に、プログラミングを学ぶことでセキュリティの専門知識を深め、より良い専門家になることができると結び付けています。

Takeaways

  • 👨‍💻 プログラミングはセキュリティの専門家にとって必ずしも必要ではなく、タスクや職種によって異なる。
  • 🔧 プログラミングを知らない場合でもセキュリティ分野で成果を上げる方法はあるが、スキルの限界に直面する可能性がある。
  • 🛠️ 昔はプログラミングを使わずにセキュリティツールを実行して問題を検出することはできたが、今日ではプログラミングが役立つ。
  • 💼 自動化されたセキュリティテストレポートを販売する会社もありますが、プログラミングを学ぶことでさらに価値を提供できる。
  • 🔑 セキュリティのスキルを向上させるためには、単なるトリックや技を学ぶだけでなく、プログラミング能力を身につけることが望ましい。
  • 🚀 プログラミングを学ぶことでセキュリティの分野でより高い脆弱性にアクセスできるようになる。
  • 🛡️ クラウドセキュリティなどの分野では、プログラミングは必要ない場合もあるが、プログラミング能力は役立つ。
  • 🔍 コードレビューやセキュリティ_AUDITINGでは、プログラミング能力が重要で、自動化されたツールの結果を理解するために必要。
  • 🌐 ネットワークセキュリティにおいても、プログラミング能力は有用で、自動化されたリコンnaisanceなどを行う際に欠かせない。
  • 🛠️ セキュリティにおけるツールの構築やファザーの開発にはプログラミング能力が必要で、それらを効果的に使用するためには理解が必要。
  • 🔄 自動化はセキュリティの様々なタスクで重要な役割を果たし、プログラミング能力がその自動化を可能にする。
  • 🔑 プログラミングを学ぶことでセキュリティの専門家は、問題解決能力や思考力が向上し、セキュリティの分野でより価値ある存在になる。

Q & A

  • このディスカッションシリーズはどの頻度でリリースされますか?

    -このディスカッションシリーズは隔週木曜日にリリースされます。

  • プログラミングはセキュリティの仕事に必要ですか?

    -プログラミングは必ずしも必要ではありませんが、仕事の種類やタスクによります。プログラミングが役立つ場面は多いです。

  • セキュリティの分野でプログラミングが必要でない場合はどのような仕事がありますか?

    -クラウドセキュリティやIAM(Identity and Access Management)の権限管理など、プログラミングが必ずしも必要でない仕事があります。

  • プログラミングスキルがない場合、セキュリティの仕事でどのような制約がありますか?

    -プログラミングスキルがないと、より高度な脆弱性を見つけることや、自動化されたツールを効果的に使用することが難しくなります。

  • セキュリティの仕事でプログラミングが役立つ理由は何ですか?

    -プログラミングは、ツールの構築、スキャンの結果の理解、脆弱性のトリアージなど、多くの場面で役立ちます。また、プログラムの自動化により、作業の効率が向上します。

  • プログラミングができない場合、どのような方法で脆弱性を見つけることができますか?

    -基本的なトリックを学ぶことで、いくつかの脆弱性を見つけることができます。しかし、そのような方法では高度な脆弱性を見逃す可能性があります。

  • コードレビューを行う際にプログラミングスキルが必要な理由は何ですか?

    -コードレビューでは、コードを理解し、潜在的な脆弱性を特定するためにプログラミングスキルが必要です。

  • セキュリティの仕事でどのようなプログラミング言語を学ぶべきですか?

    -C言語などのネイティブ言語、オブジェクト指向言語(例:Java、.NET)、および機能言語を学ぶことをお勧めします。

  • セキュリティの仕事において、自動化が重要である理由は何ですか?

    -自動化は、スキャン、リコン(偵察)、および脆弱性の特定など、多くのタスクを効率的に行うために重要です。

  • セキュリティの分野でのスクリプトキディとは何ですか?

    -スクリプトキディとは、他人が作成した既存のツールやスクリプトを使用して脆弱性を探す人のことを指します。独自のスキルや知識が乏しい場合が多いです。

Outlines

00:00

💻 プログラミングとセキュリティの関係

この段落では、プログラミングがセキュリティ仕事に必要なスキルかどうかについて議論されています。議論者は、プログラミングが必ずしも必要なわけではなく、タスクやジョブによって異なると述べています。しかし、プログラミングを知らない場合、セキュリティ分野で不利になる可能性があると指摘しています。過去10〜15年ほど前には、既存のツールを実行するだけでセキュリティの分析ができた時代がありましたが、今日ではプログラミングが多くの場面で役立つと語っています。

05:02

🔒 プログラミングスキルの欠如とセキュリティ

この段落では、プログラミングスキルがなくてもセキュリティの基本的な分析は可能であるが、そのスキルがないとセキュリティの上限に達することが困難であると述べています。プログラミングを知らない場合、特定の脆弱性を見つけることができないという問題や、セキュリティのスキルを向上させるためにプログラミングスキルが必要であることが強調されています。また、クラウドセキュリティやIAMの例を挙げ、プログラミングが役立つ場面があると述べています。

10:02

🛡️ 防御側でのプログラミングの重要性

この段落では、防御側のセキュリティ分野でプログラミングがより必要であると主張しています。プログラミングを知らない場合、特定のタスクを実行することは可能ですが、システム管理の側面でスクリプト言語が必要な可能性があると述べています。また、コードレビューやペンテストツールの構築、ファザーの開発など、プログラミングスキルが重要であることが強調されています。

🔧 プログラミングスキルとセキュリティの関連性

最後の段落では、プログラミングスキルがセキュリティの専門知識にどのように関連しているかについて議論しています。プログラミングを知ることで、セキュリティの問題をより深く理解し、アプリケーションやネットワークの動作を把握することができます。また、プログラミングを学ぶことで、問題解決の方法や思考の方法が変わり、セキュリティ分野でのスキル向上に役立つと述べています。

Mindmap

Keywords

💡プログラミング

プログラミングとは、コンピューターが理解できる命令を記述する行為であり、ビデオの主題であるセキュリティ分野においては、必要かどうかは職種やタスクによって異なるが、知っていることは多くの場面で役立つとされています。ビデオでは、プログラミングがセキュリティの専門家にとって欠かせないスキルであると示唆しています。

💡セキュリティ

セキュリティとは、コンピューターシステムやネットワークに対する不正アクセスや攻撃から保護する行為を指し、ビデオではプログラミングスキルがセキュリティ分野で役立つかどうかが議論されています。プログラミングはセキュリティツールの開発や脆弱性の検出に役立つと示されています。

💡ハッキング

ハッキングとは、通常は未承認でコンピューターシステムにアクセスすることを指し、ビデオではプログラミングスキルがハッキング行為に欠かせないものであるかどうかについて触れています。過去にはツールを単純に実行するだけでハッキングができた時代があったが、現在ではより高度なスキルが求められています。

💡自動化

自動化とは、手動での操作を機械やソフトウェアに委ねることで、ビデオではセキュリティ分野での自動化が進歩をもたらしているとされ、プログラミングスキルがその一環として重要であることが強調されています。例えば、自動化されたペンテストや脆弱性スキャナーの使用が挙げられます。

💡セキュリティツール

セキュリティツールとは、脆弱性検出やネットワーク監視などのセキュリティ関連のタスクを支援するソフトウェアを指し、ビデオではこれらのツールを効果的に使用するためには、プログラミングスキルが必要であることが示されています。

💡コードレビュー

コードレビューとは、ソフトウェアのソースコードを分析し、品質やセキュリティホールを特定するプロセスであり、ビデオではプログラミングスキルがこのプロセスで重要な役割を果たすことが強調されています。コードレビューはセキュリティを確保するための重要なステップです。

💡脆弱性

脆弱性とは、ソフトウェアやシステムに存在するセキュリティ上の欠陥を指し、ビデオではプログラミングスキルが脆弱性の特定や修正に役立つとされています。特に、ウェブアプリケーションのセキュリティを確保するためには、プログラミング能力が不可欠です。

💡スクリプト・キティ

スクリプト・キティとは、プログラミング能力がなく、既存のスクリプトやツールだけを使って攻撃を行う人を指し、ビデオではこの単純なアプローチではセキュリティの高度なスキルを習得できないことが警告されています。

💡クラウドセキュリティ

クラウドセキュリティとは、クラウド環境におけるデータやリソースの保護に関するセキュリティを指し、ビデオではIAM(Identity and Access Management)などのクラウドサービスの管理にプログラミングスキルが役立つとされています。

💡ファザー

ファザーとは、ソフトウェアのバグを見つけるためにランダムなデータを生成するプログラムであり、ビデオではプログラミングスキルがファザーの開発や使用に必要不可欠であることが示されています。ファザーはセキュリティテストの重要なツールとして位置付けられています。

Highlights

The necessity of programming in security work varies depending on the job or task.

Not knowing programming can put one at a disadvantage in modern security practices.

A decade ago, one could manage without extensive programming knowledge by using existing tools.

There are security tasks, such as using automated pen test reports, that can be done without programming but are less valuable.

Learning basic tricks can lead to finding vulnerabilities but limits one's skill ceiling.

Programming knowledge helps in creating and understanding custom tools and scripts for security.

Script kiddies, who rely on existing exploit scripts, limit their potential in security.

Some areas of security, like cloud security with IAM permissions, may not require programming but can benefit from it.

Programming is more necessary on the defensive side for tasks like automating system administration.

Code review and auditing are significantly enhanced with programming skills.

Understanding code is crucial for effectively triaging findings from automated tools.

Fuzzing has become a standard part of vulnerability research and requires programming.

Manual auditing is essential, but fuzzers provide additional findings that are now part of the process.

Triage skills are necessary for understanding and acting on the results of security scans.

Programming knowledge helps in visualizing how applications are built and how they might be exploited.

Having a basic understanding of programming is sufficient for most security roles.

Programming teaches problem-solving skills that can be applied to security.

For code reviews, having experience with multiple programming languages is beneficial.

Upcoming video will discuss which programming languages are good for security and their reasons.

Learning to program is recommended for those aiming to improve their security skills.

Transcripts

play00:01

[Music]

play00:08

hello everyone

play00:09

welcome to another discussion video in

play00:11

the discussion series we're releasing

play00:12

bi-weekly on thursdays

play00:14

and this one goes into is programming

play00:16

necessary for security work

play00:18

so you know in these videos we we give

play00:20

our

play00:21

you know opinions up front and mine my

play00:23

opinion here is not necessarily it

play00:25

depends on

play00:26

uh you know the type of job or task

play00:29

you're trying to do

play00:30

um so i'll let you jump in there z and

play00:33

state what you think on that yeah i

play00:36

pretty much agree like there are areas

play00:38

of security where

play00:40

programming maybe isn't necessary

play00:44

that said you're definitely putting

play00:45

yourself at a disadvantage by not

play00:46

knowing me in this day

play00:49

programming is going to help you out in

play00:51

so many ways regardless of it being

play00:53

security

play00:54

but i mean without kind of focusing

play00:56

ourselves in on

play00:59

traditionally what you might call

play01:00

hacking um

play01:04

if you go back in time like uh you know

play01:07

10 15 years ago you could definitely get

play01:09

away without a lot of programming

play01:10

knowledge just running some of the

play01:12

existing tooling that's out there

play01:14

that was being released especially close

play01:16

to the 10 years ago

play01:17

a lot of tools coming out a lot of

play01:18

things that you can just kind of run and

play01:20

companies still

play01:21

actually make you know they'll sell just

play01:24

an automated pen test report

play01:26

you know running whatever automated

play01:28

tester they've got

play01:29

run that gets report ship it off to the

play01:32

client and charge them

play01:33

however much they want for it so you can

play01:36

still kind of make money you can still

play01:37

profit without that but

play01:39

i'm hoping most of our listeners

play01:40

actually kind of care about the skill

play01:42

that's

play01:43

part of the craft rather than just doing

play01:45

the bare minimum to get money

play01:47

uh kind of leaving yourself on the no

play01:50

side when it comes to as

play01:51

you can make money you can actually make

play01:54

a good bit of progress without needing a

play01:56

lot of programming skill

play01:57

you can learn some of the basic tricks

play01:59

you know putting in a going around the

play02:01

internet putting in a single quote into

play02:03

a bunch of text boxes

play02:04

you're probably still going to find some

play02:06

maybe not as much as you would if a

play02:08

while back but

play02:09

you're still going to find things but

play02:11

you're basically just learning a bunch

play02:12

of

play02:13

tricks to do that so like i said that

play02:14

single quote

play02:16

do the same thing with your angle

play02:17

brackets double quotes whatever

play02:19

look for cross-site scripting um looking

play02:22

for eye door type issues again just

play02:24

change a number in a url like you can

play02:26

learn these tricks you can do them you

play02:27

can find

play02:28

plenty of issues that way and actually

play02:30

be fairly

play02:33

fairly productive doing that but there's

play02:35

the skill ceiling

play02:36

um no matter what you do if you're not

play02:38

able to do any programming if you're not

play02:40

able to do anything that work yourself

play02:42

you're just limiting yourself

play02:46

yeah i mean the problem with tricks is

play02:48

it's easy to miss

play02:49

issues that wouldn't be caught by using

play02:51

those common tricks and that's like

play02:53

you know as soon as you use that trick

play02:54

you don't really know how to augment it

play02:56

or modify it to

play02:58

potentially find an issue that could

play03:00

still exist it's just not as easily

play03:02

hittable

play03:03

yeah because they have some kind of

play03:04

filter in front of it or something

play03:05

that's maybe not adequate but is

play03:07

adequate enough to prevent those tricks

play03:09

from doing anything

play03:10

yeah that's kind of the thing it's that

play03:12

part that's that skill ceiling that was

play03:14

mentioning is

play03:15

you're not at the point of being able to

play03:17

hit the harder vulnerabilities if you're

play03:18

just doing those tricks

play03:20

uh i mean it is traditionally like what

play03:24

i would call a script kitty who's doing

play03:26

that even if they are

play03:27

manually uh doing some of these exploits

play03:30

i do think with the advent of web

play03:32

exploitation script kitty has kind of

play03:34

lost its meaning just because of how

play03:38

how the web has kind of impacted

play03:40

vulnerabilities versus when

play03:42

people were just kind of running around

play03:43

with existing existing kind of released

play03:46

exploit scripts um

play03:49

that said i mean you you kind of put

play03:51

yourself into that sort of category

play03:52

you're not

play03:54

you're not providing much value

play03:57

you're just kind of you can still be

play04:00

productive though

play04:01

is i guess my main point like you can be

play04:03

productive but

play04:04

your value really isn't there it's about

play04:06

as valuable as any other company just

play04:08

running an automated scanner

play04:12

so there are some areas where i think

play04:14

programming isn't really necessary

play04:16

and uh what came to mind when i was

play04:18

thinking of this was

play04:19

on the last podcast we did which was

play04:21

episode 48 uh we we covered cloud

play04:23

security stuff

play04:24

you know with aws and talked about iam

play04:26

permissions and stuff like that

play04:28

managing those kinds of permissions i

play04:30

would still consider security and you

play04:32

don't really need

play04:33

programming experience to do um though i

play04:36

think programming experience might be

play04:37

beneficial for doing that but i don't

play04:38

think you absolutely need it

play04:41

that was one area i was kind of thinking

play04:42

of even on that podcast episode

play04:44

they uh used some programming to

play04:47

automate

play04:48

uh enumerating the various um various

play04:51

roles that they were able to access and

play04:53

definitely made heavy use of programming

play04:55

skill

play04:56

in order to do or in order to pull off

play04:59

their attack

play05:01

i mean you setting it up on the

play05:03

defensive side sure but actually i'd

play05:05

argue that on the defensive side

play05:07

programming becomes a little bit more

play05:09

necessary

play05:10

you could do that particular task

play05:12

without it

play05:13

but anybody who's doing that task is

play05:15

probably doing a lot more of the

play05:17

sysadmin side things too

play05:18

which you're probably going to want at

play05:21

least kind of your daily driver

play05:22

scripting language for that said

play05:26

i don't really want to focus on like the

play05:30

defensive side too much

play05:32

just because i haven't worked while i

play05:34

worked as a

play05:36

developer with some security folks but i

play05:37

haven't really worked on that blue side

play05:39

too actively yeah that's fair

play05:43

um my main point though is when it comes

play05:45

to auditing like code review and stuff

play05:47

like that it becomes a lot more

play05:48

important

play05:49

you know with with code review

play05:50

especially it's kind of in the name

play05:52

um you know like you were saying earlier

play05:55

there are some automated things where

play05:56

you might not necessarily need it

play05:58

you know when you're getting into like

play05:59

running meta split modules stuff like

play06:00

that

play06:01

but especially when it comes to building

play06:03

tools for pen testing

play06:04

uh building scanners fuzzers that kind

play06:07

of stuff

play06:08

you definitely need programming

play06:09

experience to be able to do and even if

play06:11

you're just running tools and not

play06:13

necessarily building them

play06:14

you want to be able to understand what

play06:16

you're looking at when you find things

play06:18

or

play06:18

you get reports from automated tooling

play06:21

so that you can triage it

play06:23

and you know in order to do that you you

play06:25

probably do need to understand the code

play06:27

to some degree

play06:28

that's actually i think a really

play06:29

important point on the

play06:31

building fuzzers kind of jumping back a

play06:33

little bit but

play06:36

automation so we're talking about

play06:38

fuzzers right now but um

play06:40

other areas like in terms of more

play06:42

general pen tasks so if you go more on

play06:44

the network security side of things

play06:46

you still need to automate like there's

play06:47

so much more automation going on when it

play06:49

comes to recon and stuff

play06:51

um and just as part of the normal task

play06:54

like there's a lot of automation that

play06:56

happens

play06:57

that you're really at a disadvantage if

play06:59

you can't

play07:00

develop your own tooling just to hit

play07:02

some endpoint to enumerate something

play07:04

whatever

play07:05

so as we're even saying with the cloud

play07:07

thing like they use some of the

play07:08

they wrote a script to enumerate what

play07:10

was available

play07:12

um through the i am rules uh

play07:16

so i mean like the programming you know

play07:18

is going to augment everything and

play07:20

these days i think you know fuzzing

play07:23

especially on the exploit development

play07:24

side of things and vulnerability

play07:26

research

play07:27

buzzing has kind of become the key thing

play07:29

that yes i mean manual auditing is still

play07:31

essential

play07:33

but having the fuzzer going having a

play07:34

fuzzer giving you some findings has just

play07:37

become a standard part of the process

play07:39

now

play07:40

uh that you basically you need

play07:42

programming in order to be able to do

play07:43

that just even on like a small

play07:46

uh small little project you know a

play07:48

little web app you just quickly script

play07:50

up all of the end points you've got and

play07:52

toss a quick fuzz right and see what

play07:53

happens

play07:55

so i mean it's definitely essential

play07:56

there going back there on your second

play07:58

point though triaging

play08:00

um yeah i mean when you're that

play08:03

also uh i guess that triaging from the

play08:05

crashes knowing the results of any of

play08:07

the scans so

play08:08

while i do kind of hate on the companies

play08:10

that just provide like a scan report

play08:13

scans are valuable there's a chance that

play08:15

it might notice something you missed but

play08:16

it's also

play08:17

it's just kind of a safety net in a

play08:20

sense like you just run it you see what

play08:22

it gives you and it might give you

play08:23

some place they're looking at manually

play08:25

and being able to understand the results

play08:27

and kind of uh

play08:28

like the term grok or intuitively

play08:30

understand the results

play08:32

being able to look at those results and

play08:33

then work off of that so when it comes

play08:35

to the triaging

play08:36

you definitely need that when you're

play08:37

looking at a crash dump or something but

play08:39

it also just comes to the output of

play08:42

any of us any scanners like you might

play08:45

understand that saying like hey here's

play08:47

an issue and here's kind of what happens

play08:49

but how you take advantage of that issue

play08:50

to actually do something important

play08:52

is kind of where it could help to have

play08:54

the programming knowledge to understand

play08:56

how the application might be built

play08:58

what components say maybe a trust and

play09:00

just kind of have that visualization and

play09:02

i said before that intuitive

play09:06

understanding

play09:08

yeah so overall i think even though

play09:11

programming might not be necessary for

play09:12

every type of job

play09:14

it's an overall benefit and there's no

play09:16

reason not to learn it

play09:18

um because it's only going to benefit

play09:20

you right it's not going to draw back on

play09:21

you at all really

play09:22

um i do kind of want to clarify though

play09:25

when we say you know knowing programming

play09:26

and stuff i don't mean

play09:28

you know you need to become a

play09:29

full-fledged software engineer knowing

play09:31

like

play09:31

you know the ins and outs of cs and

play09:33

algorithms and all that stuff

play09:35

um unless you're auditing something

play09:37

that's specifically entrenched in those

play09:39

areas of like algorithms and whatnot

play09:41

um i think for whatever reason people

play09:44

think that if you don't know all the ins

play09:45

and outs of like devops and

play09:47

and software engineering that you can't

play09:48

do security and i think that's a little

play09:50

bit

play09:50

too far past the line um i just don't

play09:54

think that's true at all for most cases

play09:57

yeah for a lot of security i mean you're

play09:59

not

play10:00

you need to have a general understanding

play10:02

about how applications are built kind of

play10:04

what's going on behind the scenes

play10:05

especially when you're dealing with like

play10:07

a black box environment

play10:08

where you see the ui but you haven't

play10:11

really gone in or you can't in some

play10:12

cases reverse engineer the actual code

play10:15

but you can look at what's happening on

play10:16

the front and be like okay this is

play10:18

probably this in the back end

play10:20

how this kind of works how this fits

play10:21

together so you need to understand how

play10:23

applications are kind of built or how

play10:26

networks are configured on like the

play10:28

network security side of things you

play10:30

don't need to be like the greatest

play10:32

programmer and being like a amazing

play10:35

programmer

play10:36

doesn't translate into security ability

play10:38

either

play10:40

uh no doubt having that understanding

play10:42

helps

play10:44

but i mean there's kind of the

play10:46

diminishing returns at a certain point

play10:48

once you kind of have your basics down

play10:50

security becomes reasonably accessible

play10:52

like if you could build a similar app to

play10:54

what you're targeting

play10:57

um and by similar i do mean like much

play10:59

lesser quality

play11:00

you know like i don't expect you to know

play11:02

how to write

play11:03

like a full-scale linux kernel uh before

play11:07

you can actually start attacking it but

play11:08

like if you

play11:09

understand the basics of operating

play11:10

systems it's at least approachable to

play11:13

you

play11:14

then you can start jumping into the

play11:15

security side of things

play11:18

and a point i'll throw on there too is

play11:20

just the the programmer way of

play11:22

you know thinking and problem solving in

play11:24

and of itself

play11:25

uh can be useful for figuring how to how

play11:28

figuring out how somebody would like try

play11:30

to circumvent permissions or something

play11:31

for example

play11:32

so even where programming isn't used

play11:34

directly what it teaches you and the way

play11:36

of thinking

play11:37

it it you know molds you to think

play11:40

i think that could be transferable so

play11:44

yeah and i guess one other things you

play11:46

know if you're doing a code review you

play11:47

kind of need to know how to program

play11:50

part of the thing is actually on that

play11:51

note

play11:53

you don't you don't necessarily need to

play11:55

be as we've already said like the most

play11:57

amazing programmer out there

play12:00

you do kind of need some experience with

play12:02

different languages though

play12:03

usually somebody who's done security

play12:05

isn't just going to know one language

play12:08

i think some areas you can kind of get

play12:09

away with a single language where it

play12:11

comes down to like automating recon and

play12:13

stuff you can maybe get away with just

play12:14

some like python or like that daily

play12:16

drive

play12:17

language uh but when it comes if you're

play12:20

doing kind of the code review

play12:22

level doing doing stuff at that level

play12:25

you kind of need to have an

play12:27

understanding of several different

play12:28

languages

play12:30

rather than just one but um

play12:33

you'll start noticing a lot of

play12:34

similarities between languages so you're

play12:36

kind of able to pick things up

play12:38

really quickly once you've kind of

play12:39

started learning one or two languages um

play12:41

i tend to recommend like a um

play12:45

a native language like c and then learn

play12:48

object oriented because

play12:49

it's used all over in enterprise

play12:51

code.net stuff is using it java stuff

play12:55

um so like you see those two a lot and

play12:57

then a functional language kind of

play12:59

be an edge case on some of the other

play13:00

weird things you might run into and

play13:02

that kind of catches you up on uh

play13:06

most things you're going to run into in

play13:07

terms of like doing code reviews uh

play13:09

you'll be able to pick up

play13:10

almost any language if you kind of have

play13:12

those fundamentals

play13:16

so our next video will be going into

play13:18

programming languages

play13:19

and you know which ones are good to know

play13:20

for security and for what reasons and

play13:22

stuff like that so keep a look out for

play13:24

that

play13:24

in uh in the next two weeks time that

play13:27

way you know you can

play13:28

you can get kind of both parts to uh

play13:30

this discussion

play13:31

that said i think on this discussion

play13:33

specifically we'll we'll wrap it up here

play13:35

unless you have any last-minute thoughts

play13:36

see no

play13:38

i guess i would just end off by saying

play13:40

if you want to actually you know get

play13:42

good

play13:43

and have some decent skill which i think

play13:46

you should probably aim for

play13:47

yes just start learning to program if

play13:50

you don't know that already

play13:52

all right so i'll end off by saying we

play13:54

do have our

play13:56

day zero podcast if some of you you know

play13:58

haven't heard of that

play13:59

we we run those on monday at 3 pm

play14:01

eastern 12 pm pacific

play14:02

so check those out if you haven't

play14:04

already we also have these discussion

play14:06

videos every two weeks on thursdays

play14:08

usually they're released around the

play14:10

morning i think around 8 a.m or so is

play14:11

when we try to get them out

play14:12

so keep a lookout for those other than

play14:14

that though we will see you guys in the

play14:16

next discussion video

Rate This

5.0 / 5 (0 votes)

Related Tags
プログラミングセキュリティハッキングツールコードレビュー自動化スキルウェブセキュリティセキュリティ分析技術トリック
Do you need a summary in English?