Security should be handled in the script, as mentioned in previous posts. Even if you block access to a table (and there's no easy way to do this), the user can still see the underlying values, for example by creating their own version of the table using Insight Manager, via duplication, or by viewing the underlying field values in the Selections screen.
If you want to try for "Security through obscurity", you can use a show/hide container and hide the table based on whatever rule you want, e.g. using the OSUser() function. This isn't actually security, though.
