The “Filename Zip” access and “dosubl” are nice new functions. The”lockdown” for administrators however is a very doubtful approach. Very often the dangerous use administrators see is the SAS usage as a whole. They want to lockdown the SAS usage, getting rid of that.
Coming into a situation seen SAS as opening up all data without control and being too difficult and expensive (Gartner reports under cautions) to operate, is bad promotion-sales for the market position.

The real problem is that the people at SAS architects, product managers, decisions makers are missing the growing importance on “data governance” and more in detail “standard of good practice” generic guidelines. Security should be there by design. It is not something to be done as a bug-fix. There are many references
http://owasp.org (nist docs http://nist.gov ,sans https://www.sans.org/critical-security-controls/)
http://istwb.org (technical application test, see the glossary) and many more.

As SAS cannot and is not allowed to overrule The OS security, Windows, Unix and a likes and the involved DBMS. It will be a DOA (Dead On Arrival) to promote something in this direction.
The better approach would be to try to get those security requirements to be fulfilled in a normal way according the common guidelines. It is needing to build it up from all involved technical layers, Using their controls, up to the daily usage.