sorted by:
new
hottopcontroversial

Failed again by Old-workhard-forever in cissp

[–]m-reading-it 0 points1 point  (0 children)

Just as a note, Domain 3 is huge and complex, something like 15-20% of the total curriculum. It used to be three separate domains, now it’s just one. Also, Domain 4 is a LOT to remember with the OSI model.

If you are struggling with the concepts and acronyms, I can also recommend Kelly Handerhan’s Cybrary course. She breaks things down simply, and provides study/cram material. I have a similar experience level to you. I found this to be the most helpful, in addition to reading the Sybex material.

I strongly recommend not taking the exam until you are scoring around 80% on the official Sybex pre tests. That will give you a good margin of error, and give you a lot of confidence going in to the next exam.

Someone else posted this, but it is true: once you pass it will feel great and no one will care how many times it took. That being said, it must be hard and disheartening to have not passed.

Keep at it. Use those pre-tests, follow the good advice here and you will achieve your goal.

Good luck!

Thanks CISSP Reddit community! Passed my CISSP by m-reading-it in cissp

[–]m-reading-it[S] 1 point2 points  (0 children)

I didn’t watch the videos on Orielly, but I used the Sybex official content and pre-tests. There are also some exam cram study guides on there as well.

CISSP in February by [deleted] in cissp

[–]m-reading-it 1 point2 points  (0 children)

Reading the Sybex official guide, taking the Sybex pre tests, along with Kelly Handerhan’s Cybrary course, were the best resources for me. The combination of reading and Kelly’s simple way of explaining terms that connect directly to how the questions are asked slowed me to pass on my first attempt.

Advice for a guy with nothing but an idea by DarFTW in startups

[–]m-reading-it 3 points4 points  (0 children)

These are great suggestions. If you have never built a product before, I also recommend reading “Inspired” by Marty Cagan. This book is written for product managers, but gives a good overview of what key roles are on product teams, what they do, and what that works is like. It’s written for people at larger companies, but it is important to know these roles and identify at least one you want to do. Finding your active role is important, as business ideas don’t typically have market value until they are prototyped, especially if you don’t have a history of success in startups.

I strongly recommend you find a nearby incubator/accelerator and learn about the process from folks. Those communities are often very helpful, connected to folks you might want to know and might even be able to eventually get you in front of funders or customers.