ORACLE SOLARIS 11.4 REVIEW RECORD Yenra | September 7, 2026 Guide: https://yenra.com/solaris-security/ HOW TO USE For an authorized administrator reviewing Solaris 11.4. Attribute evidence to the host or zone examined. Keep secrets and sensitive identifiers in controlled records. Use current release-specific Oracle guidance. Review proposed changes, validation and recovery before implementation; record exceptions with owners and review dates. RECORD Copy the repeatable task/run fields for each observation. Keep the units shown. 1. Review date/owner; private system reference; application owner; host/zone scope ____________________________________________________________ ____________________________________________________________ 2. Installed release/update evidence: pkg info entire (read-only) ____________________________________________________________ ____________________________________________________________ 3. Version; branch; publisher; state; full package identifier; collection date ____________________________________________________________ ____________________________________________________________ 4. Applicable update/support/repository evidence; application constraints ____________________________________________________________ ____________________________________________________________ 5. Accounts/roles: purpose, owner, required rights, decision ____________________________________________________________ ____________________________________________________________ 6. Services: purpose, permitted clients, dependencies, evidence ____________________________________________________________ ____________________________________________________________ 7. Monitoring: test event, timestamp, destination, retrieval, reviewer, capacity ____________________________________________________________ ____________________________________________________________ 8. Finding: evidence, impact, proposed action, validation and rollback ____________________________________________________________ ____________________________________________________________ 9. Recovery: required data/keys, restore test result/time, remaining gap ____________________________________________________________ ____________________________________________________________ 10. Exception: reason, compensating measure, owner, expiry/review date ____________________________________________________________ ____________________________________________________________ 11. Final actions; responsible owners; validation evidence; next review trigger ____________________________________________________________ ____________________________________________________________ WORKED EXAMPLE (ILLUSTRATIVE, NOT MEASURED RESULTS) Illustrative access change: confirm required export clients, test a narrower rule in a representative environment, verify an allowed export and a denied test client, check monitoring and rollback, then schedule the reviewed change. SOURCE CONTEXT Use the linked guide for explanation and these exact-source documents for model/version-specific behavior. Recheck current documentation before a change. https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/11.4/update-sys-add-sw/displaying-package-description-when-packaged-installed-full-fmri.html https://www.oracle.com/solaris/technologies/solaris11-product-documentation.html https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/11.4/security-guidelines/configuring-oracle-solaris-security.html https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/11.4/security-guidelines/maintaining-and-monitoring-oracle-solaris-security.html