Stephen Schneiter said:

Hi @Ronald, Thanks for the inquiry. There has never been any requirement to be a CompTIA Trainer or a Certified CompTIA Trainer. I would like to have one, as I think it helps trainers stand out when promoting their skills. CompTIA has always suggested that a trainer hold the certification they are teaching, which I highly agree with. However, there are no official rules for being able to teach towards CompTIA Certifications.

The CTT+ certification was geared primarily toward folks coming from industry moving into the training field. The goal was to provide skills for managing a training environment and technologies used to deliver content and engage students. While this certification was good for proving the holder had the skills required to deliver a course successfully, CompTIA never required a trainer to hold the certification.

CompTIA actually retired and dropped the CTT+ certification. It desperately needed to be updated to current training delivery technologies, and the cost to update the product was just too high compared to the overall lack of interest in the certification.

CompTIA is developing a training delivery course that, when completed, will serve as a training course for those looking to enter the training field. The course will be just that: a short training course without a high-stakes certification. I do not have any update on when this type of course will be publically available. We will definitely keep you posted on any announcements!

With that said, what are the thoughts of the community? What do you think should be offered? Do you think a stand-alone certification similar to CTT+ would be of value? Who would sit for the certification?

Looking forward to the feedback!

Click to expand...

Ronald said:

I hope you’re all doing well. Are there any new requirements or programs from CompTIA for becoming a trainer, especially since CompTIA Trainer+ is no longer available?

Thanks in advance for any insights!

Tagging @Rick Butler and @Stephen Schneiter for insights. Thanks in advance for any information.

Click to expand...

precious said:

I've found that students often struggle with practical applications of pentesting tools. One way I make this easier is by using Kali Linux labs to demonstrate real-world scenarios. For example, I set up a vulnerable machine using Metasploitable and have students practice using Nmap for network discovery and Metasploit for exploitation. I also encourage them to experiment with EvilPDF for embedding payloads into PDFs, which ties in nicely with social engineering topics. Does anyone have tips on simulating phishing attacks for teaching purposes?

Click to expand...

Tobias Kipkorir said:

Excited that TTT and CIN resources helped me so much for my network certification prep! These two solidified my understanding of core fundamentals. See you at Tech+!

Click to expand...

Jill West said:

Just to clarify...

If we passed the Cloud+ beta, we cannot then take the regular exam once released, right? Thanks!

Click to expand...

MBA said:

You can use the open-source phishing framework, GoPhish, getgophish.com.

Click to expand...

Carnegie said:

@Brian Ford, great tips. A favorite troubleshooting Windows command line tool is PathPing that combines ping and traceroute into one tool.

Code:

Usage: pathping [-g host-list] [-h maximum_hops] [-i address] [-n]
                [-p period] [-q num_queries] [-w timeout]
                [-4] [-6] target_name

Options:
    -g host-list     Loose source route along host-list.
    -h maximum_hops  Maximum number of hops to search for target.
    -i address       Use the specified source address.
    -n               Do not resolve addresses to hostnames.
    -p period        Wait period milliseconds between pings.
    -q num_queries   Number of queries per hop.
    -w timeout       Wait timeout milliseconds for each reply.
    -4               Force using IPv4.
    -6               Force using IPv6.

Click to expand...

Rick Butler said:

When I've taught routing, I always started on the whiteboard, building a pseudo table to teach the very basics and move on from there.

I've always taught that if you can avoid a static entry on a routing table, if there's any way, do so - routing protocols are smarter. And if you have to have a static entry, document the heck out of it, so someone that comes behind knows. The way I see it, these days, if you have to use a static entry, you're trying to do something unconventional or weird.

That's where the documentation comes in - because "well, it was a good idea when I put it in there" will turn into "what the heck was this fool thinking?". In the OP's example, I think that entry was correct at one time, that it was working once and then one day, it wasn't working. Perhaps the gateway was changed, but no one bothered to look at the static routes in the other routers.

However, these bugs are also great to teach. Using something like GNS3 to build a network up and test with, has been a mainstay for me over the years.

/r

Click to expand...

Brian Ford said:

To expand on Trevor's answer about looking at the logs; investigate the routing issue by determining the scope of the problem. Expand on this by using ping and traceroute. Can users connect to some networks (sites) but not others? Statics are often used in two scenarios. #1 when the network is really simple and the architect wants to dictate the traffic path (think about a simple home /office router or a network with one ISP connection). Another use case is when the network is more complex and multiple paths (multiple ISPs) exist between two networks. In this case you might want to override or backup the route discovered via a routing protocol. And this is where route weighting comes in to the discussion.

Click to expand...

Usage: pathping [-g host-list] [-h maximum_hops] [-i address] [-n]
                [-p period] [-q num_queries] [-w timeout]
                [-4] [-6] target_name

Options:
    -g host-list     Loose source route along host-list.
    -h maximum_hops  Maximum number of hops to search for target.
    -i address       Use the specified source address.
    -n               Do not resolve addresses to hostnames.
    -p period        Wait period milliseconds between pings.
    -q num_queries   Number of queries per hop.
    -w timeout       Wait timeout milliseconds for each reply.
    -4               Force using IPv4.
    -6               Force using IPv6.