I'm not sure Microsoft or Sony would put in much effort beyond an EULA that absolves them of all liability should an unauthorized mod brick your console, or make NPCs get naked and nasty. Kind of like what they do when you try to mod games on the 360 or PS3, I imagine.

Yup, then you would know more about it then I. Do you create the collision mesh inside the 3D software and add it as an element to said model, or do you just assign a collision mesh afterwards? I modded a bit but didnt work with the asset pipeline much.

You are very sadly mistaken. There is BIG difference between a six mod made with official tools being played on an Xbox One showing up on national news (no doubt exaggerated beyond belief by Fox News) and some modded consoles getting their LIVE accounts banned. Don't get me wrong, the disclaimer and ban hammer threats will be there but that's NOT what the console manufacturers want to avoid. It's the PR nightmare that users running self-made software mods on their systems (or rendering thousands of systems non-functional via mistake or intentional) will generate.

The idea that a user could download an add-on to a purchased piece of software and potentially render their game or possibly even their console non-functional is something a company could NEVER reply with, "I told you so....". Even the act of banning online accounts from users that actively attempt to thwart the rules would cause PR issues they would no doubt want to avoid if possible.

Interesting times, indeed.

The collsion mesh clearly has to be made with the original mesh in Blender. As I wrote already for simple meshes you can use a copy of the orignal one and scale it. For complex ones sure there is more work.

Hopefully the new engine/hardware is powerful enough, because collision meshes were always annoying for me to make.

They don't really need to put any security into the Creation Kit. To the best of my knowledge, the consoles are pretty much closed systems, in that you can't just fire up a browser on them, navigate to any site you like and download any file you like. [edit - Or at least, download any file and include it in a game folder]

Mods for consoles will be hosted by Bethesda, and delivered to the console from Bethesda.net (at least, that's what I gather from what I've read), probably via a souped up game launcher or 'browse mods' option in the game's main menu. And since Bethesda will host them, Bethesda can review them before making them available.

I'd guess there'll be a submissions process, where a mod creator uploads a mod to Bethesda.net, and if it passes muster then it'll be made available to console users. Since this distribution infrastructure will come after the release of the modding tools, by the time console users get mods there'll already be a collection on Steamworks, so Bethesda can pre-approve and upload a good selection of those for console users to keep them supplied while new mods get approved.

The approval process could, to be honest, be pretty light handed. A quick check to see if they contain six/nudity (most of those mods will announce it up-front, because that'll be the point of the mod), perhaps an automated check to make sure no cells contain vastly too many objects, the textures are reasonable sizes etc. I doubt they'll bother with checking scripting or quest design, as that would be way too much QA work.

I'm pretty sure that Bethesda has already said that citation will be kept to a minimum. In other words, if it doesn't violate copyright laws or the consoles rules, it'll probably be allowed through. Todd has also said that they're going to allow console gamers to break their game, just like PC gamers can. However, there will be a system in place so that they won't completely lose everything when that does happen.