scott, Now your hi-jacked subject to security. The best place to secure assets is at the assets themselfes. This is an open door sorry for that. As most assets areon the OS-level, txt html rtf files are also assets the OS-security is mandatory. OLAP/Cubes is failing to define the assets in a clear way. That is by design of cubes. The cubes contain information you may and may not have access to. At the same time the higher aggreagation levels are allowed, this is a contradiction. This contradiction trying to solve is a terrible challenge as it implies row-level security. Some RDBMS systems have the option of this granularity. The problem is that rowl-level security is dependent of content/value. SAS has row-level security as a programmatical approach implemented. By that the original table must be protected to having no access by them in an other way. SAS introduced metadata-bound libraries. trying to force metadatacontrols. Stlli when the original table can be copied it could be decrypted. It is bad seurity as based on not knowing how it works and very small limited user base, so bad guys are not interested. Same applies for the pwencode promotion. As SAS is trying to fulfill programmer requests without thorougly thinking and design they are easily doing a bad security job.
... View more
