I think the arguments for SQL Server's row-level security are:
- it allows you to control access to your data without changing your schema
- it is specifically for access control, and can be managed separately from the schema
- it can cover inserts, updates and deletes, which can be difficult or impossible with views
However, I find SQL Server's approach somewhat inflexible, and I think Gallium Data can add value in some scenarios -- hence this article.
I think of Gallium Data as a middle ground between databases and applications. If you can solve your problem from either end, then that's probably the best approach, but if you can't, Gallium Data may be a life saver.