For a website, sometime we used more than a script that separated, yes separated and dont have connection at all each other

for example
domain.com is a forum, using vbulletin
domain.com/blog is a blog, using wordpress
domain.com/store is ecommerce, using oscommerce
domain.com/article is article cms, using joomla
etc


so for security best practice, like if one of the script get hacked or get something wrong,
another script files in another folder,
and another mysql database,
is still secure


can we do that? if so how to do that actually? its looks like simple and basic, but i am still not sure how to do it

if there is tutorial link please let me know too, still cant found it

It's nothing to do with security or anything of the sort.

It's just that you can only have one "index.php" file in a folder.

can we do that? if so how to do that actually? its looks like simple and basic,

Yep;

you create a folder called "blog" and install Wordpress in it.
OR
you create a folder called "article" and install Joomla in it.


I'm sure you can workout the rest from there onwards. AND if you can't you shouldn't be running any kind of website!!

Originally Posted by chrishirst

It's nothing to do with security or anything of the sort.

It's just that you can only have one "index.php" file in a folder.


Yep;

you create a folder called "blog" and install Wordpress in it.
OR
you create a folder called "article" and install Joomla in it.


I'm sure you can workout the rest from there onwards. AND if you can't you shouldn't be running any kind of website!!

no you are missunderstanding, i know how to create new folder and install scripts generally, its basic thing

what i am asking is how to make the scripts access separated, its intermediate-advanced thing,
so if one of the script got hacked for example outdated worpress (in domain.com/blog), but other scripts still save, cant accessed by the hacker, for example joomla (in domain.com/article)

what i am asking is how to make the scripts access separated, its intermediate-advanced thing,

They are seperate, installing them in sub-folders doesn't make them connected.

Basketmen -

I believe that what you are looking for, if I understand correctly, is typically known as a "chroot jail". This would essentially lock users who are able to exploit shell acess from an insecure library or network service into a particular directory.

Combining chroot with a hardened kernel that supports a mandatory access control architecture such as SELinux will have you well on your way to hosting a system that is simply not worth the trouble of penetrating for your average script-kid.

Hope this helps - let us know if there is anything else we can do to point you in the right direction!

There are ways to avoid shell exploits.

A: Use jailed/gaoled shell for the account. Your host should have done this in a shared environment.

B: Disable password authentication for shell access and use private key authentication instead.

c: Move SSH off of it's default port 22. Again something a hosting company should do.