You can never (in practice and under usual economic border conditions) make closed source secure. On the other hand, while you must make it open in order for it to be possibly secure, you must do other things in addition.
Really, get a grip on basic logic and stop claiming bullshit.
Sorry, but I've spent WAY too much time over the last year or two dealing with huge vulnerabilities in open source to believe any of the stuff you are spouting. OpenSSL alone (Heartbleed and several other critical flaws) has cost me a huge amount of time, and that's one of those open source security related products that theoretically will attract the most auditing attention and should be "secure due to the number of eyeballs theoretically always auditing it". Yet despite being open, it has not become secure, or even close to secure.
On my web hosting team (which hosts thousands of websites and uses both Linux and Windows), we have spent far less time over the last couple of years patching or dealing with closed source critical Windows vulnerabilities than we have spent on various open source critical vulnerabilities. Things always go in cycles, and probably we'll have a year here soon where Windows racks up the most major headaches again, but the point is, there's no way you can claim you can "never make closed source secure" but that "making it open could make it possibly secure if you take some additional steps". That's all nonsense. Neither model is any better than the other when it comes to security, and neither can ever be made totally secure, especially as complexity continues to rise.
Open source has its benefits, but security has never been one of them, as recent history demonstrates. It just seemed that way for a while when it had less of an install base. Now that everyone, even commercial products, are embedding open source packages like OpenSSL into them, the target base is easily big enough to invite the black hat attention, and we see that things are basically the same as they are for closed source packages with a large install base.
PS - The Linux foundation is working with researchers to make a huge push to audit OpenSSL to look for issues. This, again, proves things are the same between open and closed source. Windows gets repeatedly, badly owned, and Bill Gates writes his secure computing memo directing a huge amount of resources at security training and auditing, and things do actually improve (though they are never perfect). Now, OpenSSL gets owned, someone directs huge resources at it, and it will probably improve, in the same way and for the same reasons as closed source. Put the resources behind it, you can improve security, but without a dedicated, directed push, things slide in both models because programmers, whether in closed or open shops, are in general are fairly lazy and like new shiny things, and don't really enjoy doing mundane boring tasks like auditing old code.