You could configure suPHP. This will execute PHP scripts with the permissions of the file owner.
In your current configuration, all PHP code will be executed with the permissions of the apache user. In a shared hosting environment, this isn't a Good Thing. If it's not a shared environment, you probably don't need to worry too much.
As an example:
Let's say you have 2 users, bob and tom with websites configured on your sever. Their document roots sit at
/home/bob/public_html
/home/tom/public_html
Bob wants to add an uploads
folder to his site so he can upload stuff. So he sets up
/home/bob/public_html/uploads
This folder must be writable by apache
Well, now you have a situation where tom can write to bob's uploads folder as scripts in both their sites are being executed as apache
which has write access to bob's uploads folder. He needs to know the path, but that's not necessarily a difficulat thing to figure out.
Once you configure suPHP, the script in tom's site is run as tom, so he can't write to bob's uploads folder, unless bob wants him too.