For example, customer credit card numbers should only be passed to the card-processing facility, while your SQL DBMS connection password should only be passed to the database. They should both be marked as "restricted", but you don't want to let them cross-contaminate. (Unless you explicitly enable that.)
Instead of a flag or an incremental level, something along the lines of categories might be more useful -- this data is restricted as "customer private" while that other data is marked as "server internals", and only channels/objects which are approved for that category can access them.
More generally, you might want to look at Capabilities for a more sophisticated way of building an access control model.
In reply to Re: 'Restricted' data, an additional security mechanism for Perl.
by simonm
in thread 'Restricted' data, an additional security mechanism for Perl.
by pjf
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |