Certificates - CompTIA Security+ SY0-701 - 1.4

Security+ Training Course Index: professormesse...
Professor Messer’s Course Notes: professormesse...
- - - -
We use certificates to provide trust when accessing other devices or services. In this video, you'll learn about digital certificates, certificate signing requests, key revocation, OCSP stapling, and more.
- - -
Subscribe to get the latest videos: professormesse...
Calendar of live events: www.professorm...
FOLLOW PROFESSOR MESSER:
Professor Messer official website: www.professorm...
Twitter: www.professorm...
Facebook: www.professorm...
Instagram: www.professorm...
LinkedIn: www.professorm...

[@ghostofahorseunderthechandlier]

whew , first domain done . the past 18 videos essentially (and more efficiently) covered everything i learned in 2-3 years of my cybersecurity community college course lol

[@tboxcupcakes]

yeah i did a "boot camp" and this is teaching me more than the boot camp did. Don't get me wrong, still a good course but prof messer goes into depth more

[@CyOfficial0x]

I feel proud of myself because I completed the first domain of SY0-701. I'll rewatch the first domain to strengthen my understanding of the basics.

[@Richard-r7u6c]

No rush, take your time. Go through the content as slow as you need and write down solid notes after you've grasped what is being taught.

[@yourownbox]

KZbin, owned by Google (Alphabet), is its own Certificate Authority. They sign their own certificates, which is interesting. They are basically saying you can trust this website because we say so and there is no need to ask anyone else.

[@ivmonday]

Don't see anything wrong with it, it leverages reputation as a form of trust.

[@Exinthevatica-rq6vs]

Monopoly.

[@eeka_droid]

Yes, it can happen in some cases and it's known as the "trust me bro" certification protocol

[@maximilianoponce5388]

Thank you Professor Messer

[@SuperNotaku]

Learning alot on each video. I have to take my time and replay some of these cause how condense the terms are and what they do.

[@famaragueye5580]

Thanks Professor

[@gbemifola9980]

Thank you Prof Messer. You're such a great teacher.

[@vstrxl]

Thank you so much for these videos, Professor Messer!

[@BenedictTurton]

awesome

[@MywesternfatherAsianfath-pj4wq]

Thank you very much Professor Messer

[@girlpocalypse]

I get that you can't forge an OCSP status but what stops an operator from just preventing their applciation from updating its OCSP status once ever again once they receive the signed valid OCSP status? Do they expire?

[@girlpocalypse]

I see, they have a "next update" field. Sorry to bother you :)

[@Insight_Films927]

great amazing video

[@jcmlico]

Is there a difference between private CA and self-signed CA? As both are used internally / within the organization.

[@alexbarajas9004]

A self-signed certificate authority (CA) is an entity that signs its own certificates without involving a trusted third party. This means it can generate and validate its own certificates but is typically not trusted by default in browsers or systems because it lacks external validation. A private CA, on the other hand, is a CA that is operated within an organization for internal use. It can issue certificates for internal applications, services, or devices. While a private CA may also issue self-signed certificates, it can have its root certificate distributed and trusted across an organization, allowing internal systems to trust certificates issued by it.

[@mylesreimonenq4368]

Thank you Professor Messer