Let's audit our system, then. First, we need to audit the CPU . . . oh, wait, do you have a tunneling electron microscope, cause I don't and we need to be sure that the actual die matches the supposed schematics. So we'll have to buy 10 CPUs from different locations, and analyse 9 of them to trust the 10th one. Yeah, the AMT is in there, but you have to get that first part of the audit done first.
Now, assuming you've gotten that far, and are willing to postpone auditing the AMT for now, it's time to audit the Z170, X99, or whatever chipset you are running. Should buy several motherboards with your desired chipset, just to be sure the motherboard companies are all using the same chips, and that they are all authentic Intel Z170, B170, X99, whatevers; you'll need the VHDL or schematics here, too.
Wow, we're finally out of the motherboard and CPU combination, that's probably taken a few years off our collective lives. Time to audit the USB chip, cause it does have interrupt access to the CPU and even with all the VHDL/Verilog/Schematics there could be one of those hidden register tricks like Kjella mentioned, so we'll need to make sure that it's behaving as it should and not feeding in bad bits. Then over to the HDs, because sprite_tm showed that you could bury some malware into the drive controller and the Equation Group software has been found in those. Wouldn't want one of those chips to go un-audited.
And we have even gotten to the sound chips, the graphics cards or, oh gods, the ethernet/wifi chips. Those bastard internet I/O chips, who knows what kinds of back doors are lodged in those. For all we know, there could be a port knock code in the Intel Gigabit Ethernet chips that causes it to log all HTTPS traffic and send it out over a side channel (do the ethernet chips still have SSL accelerators, or is that a thing of the past? It plays for hyperbole, but I'm not sure where in the hardware the HTTPS decoding gets done anymore).
Seriously, have you audited any of the parts of your computer? Have you read reports from anyone else who has done any auditing? Or is this just a plea for karma? Because you don't sound informative, you sound uninformed. Every chip in your system has to be trusted, and I doubt you have attempted to audit any of them or any of the software or firmware involved either. Even with the code in hand, the long process of determining "which compiler and flags were used to build the TrueCrypt software for windows" experiment a few years ago would show you how you could have all the parts available and still have a hard time proving that the device or software you have came through a trusted source (they did eventually find the flags that built TrueCrypt and the version of MSVC used, but it took a while). That assumes that, for software, the compiler you and your provider use is not backdoored itself. Thompson's "Reflections On Trusting Trust" shows that even if you have the compiler source code, and the code for the project you want to build, and the compiler bootstrap executable, you still can't be sure that it's all "audited safe and clear".
So, there you have it. Yes, you have to trust, because it is literally outside yours, or mine, or damn near anyones to audit every system configuration out there to ensure that everyone and every device is safe. You don't trust Intel, fine. You shouldn't trust AMD, either, for the same reason. And you probably shouldn't trust SlashdotMedia, so until you can audit all of the possible data that you might get sent from the web, you might just want to disconnect from the internet. You know, to be safe from that "potential danger".