Operations, Security & Governance

Documentation ยท 1.0

Operate SAS with controlled access, secure data handling, predictable recovery, and evidence.

SAS configuration and data movement can affect external systems, shared data sets, and customer processes. Good operation therefore requires clear ownership, controlled credentials, secure data handling, review, logging, and evidence.

Operating principle: know who owns the configuration, what data it processes, what the run will change, how failure is handled, and how the result can be verified.

In this section

Security & accessHigh-level control principles for SAS configuration and data movement.Data security & data controlConnect classification, permissions, processing, monitoring, evidence, and governed AI.Run behavior & recoveryUnderstand what remains after failures and aborts.Execution visibility & loggingWhat execution information is available in each documented component.Audit, history & evidenceThe information needed to explain configuration changes, decisions, execution, and outcomes.Policies, decisions & controlsHow policy, matrices, conditions, entitlements, and Operational Activities support control.Compliance & evidenceMove from policy statements to repeatable controls and explainable evidence.TroubleshootingChoose the component that reports the problem.

View the current version in the wiki