As gerald_clark already pointed out, there is no easy answer to this question.
The direction in which you'd want to research depends on your definition of security (secure against non-permitted mofification of files, secure against reading your files from anywhere, secure against corrupting data, etc.). There are different layers in which this security may be enforced.
What I personally like about the linux philosophy, is that you can do all of your application work without root-rights (which is sometimes hard on a windows system, where you have to use mis-behaving software [which is misbehaving because microsoft does not enforce certain design paradigmas]) and that binaries, data and configuration are clearly separated (as opposed to windows, where there is no central enforced storage for these things - if you just backuped your documents, you may have lost important settings on reinstall).
Your definition of security should also include a definition of trust: whom do you trust? The Tinycore repository? Some public download server? Sourcecode which you downloaded from the - supposed - author? The linux kernel? Your filesystem?
Every action implicates trust in something, at lest in the right outcome of the commands I gave my system. When you think in depth about this, it gets harder and harder.
As an example:
I have to trust into my harddisk, that it will not fail while I don't have a backup in place. Most users I know, do not have a backup or they do it only once in a while. But when I tell you, that the chance your harddisk fails within 3 years after purchase is about 5% you may come to the conclusion, that loosing or at least corrupting your data due to harddisk failure might be more likely than an evil person hijacking your computer...