SecPod

Learn Search

Search across all Learn content

← Back to Expressions & POVs
Measures To Secure Oracle Solaris OS

Measures To Secure Oracle Solaris OS

Solaris is a Unix-based operating system developed by Sun Microsystems, which was later acquired by Oracle. Oracle Solaris OS is known for its scalability, so it can be used to handle heavy workloads efficiently and has an advanced security capability to automate self-healing (disaster recovery). Th...

Mar 12, 2020By Indumathi S3 min read

What is Solaris? Why should you use it?

Solaris is a Unix-based operating system developed by Sun Microsystems, which was later acquired by Oracle. Oracle Solaris OS is known for its scalability, so it can be used to handle heavy workloads efficiently and has an advanced security capability to automate self-healing (disaster recovery). They also come with high-core processors, which can handle multiple threads simultaneously and yet operate smoothly across databases, systems, and applications. However, they have to be updated to the latest versions every time a patch is found. A vulnerability management tool detects vulnerabilities.

How does Oracle release security advisories for Solaris?

Oracle Solaris OS provides monthly security fixes by auto patching known as Support Repository Updates(SRUs), which addresses any fixes or enhancements. It is safe to apply this fix, as it creates a backup of the boot environment, and then updates the running environment, which allows us to use the older environments when required. Fixes available in each SRU would contain all the fixes covered by its previous SRU. Ex: If SRU 12 is the newly released SRU, then it would contain all the fixes of SRU 11 and earlier.

Every quarter, these SRUs combine into a Critical Patch Update (CPU SRU), covering critical fixes including the CVE fixes. Deploying these patches will be easier with a patch management software.

The figure below shows two system upgrade strategies, where
GA = a release such as Oracle Solaris 11.2 or Oracle Solaris 11.3,
S = SRU, and
C = CPU SRU.

Figure 1: System Upgrade Strategies

To avoid the risk of successful attacks, Oracle recommends applying the patches without delay. It’s a good practice to update every time a new SRU is available or at least every quarter to the CPU SRU.

Security fixes released by Oracle for Solaris are available on a security-alert page, which contains advisory links with Critical Patch Update Advisories, Security Alerts, and Bulletins.

What do the security advisories contain?

Critical Patch Update Advisory is a collection of cumulative patches for multiple security vulnerabilities, Security Alert will address vulnerability fixes that are too critical to wait until the next Critical Patch Update and Solaris Third Party Bulletin announces patches for third-party software that is a part of Oracle Solaris distributions.

The details related to CVE fixes are in the additional information section or the notes at the bottom of each link. If multiple CVEs affects the same product, only one entry would be available in the table. With a note number linked, while mentioning others at the end of the respective link.

The CVE table released by Oracle for Solaris looks as shown in the image below.

Figure 2: CVE Table

The image below shows a notes section, which is at the end of certain advisory links.

Figure 3: Notes Section

We can refer to the NVD link for the description of the CVEs. An updated version of its product can know from the Solaris 11 Image Packaging System (IPS).

Featured Posts

Open The Most Effective Vulnerability Assessment Framework What Makes One Effective
The Most Effective Vulnerability Assessment Framework What Makes One Effective

Point of View

The Most Effective Vulnerability Assessment Framework What Makes One Effective

No single named standard makes a vulnerability assessment framework effective. This piece covers NIST, ISO, and CIS Controls, then breaks down what actually separates a working framework from a checklist, coverage, risk based prioritization, cadence, ownership, and a feedback loop.

Sep 11, 2026

Open Threat and Vulnerability Assessment How Risk Actually Gets Calculated
Threat and Vulnerability Assessment How Risk Actually Gets Calculated

Point of View

Threat and Vulnerability Assessment How Risk Actually Gets Calculated

A vulnerability alone doesn't tell the whole risk story. This piece breaks down how a threat and vulnerability assessment pairs technical weaknesses with real attacker context, walks through the six step process, and covers frameworks like NIST 800-30 and ISO 27005.

Sep 11, 2026

Open Vulnerability Assessment Services: What to Look For
Vulnerability Assessment Services: What to Look For

Point of View

Vulnerability Assessment Services: What to Look For

Choosing a vulnerability assessment provider means asking about actual coverage, scan frequency, and whether findings come with real prioritization or just a CVSS dump. This piece breaks down what strong vulnerability assessment services include, red flags to avoid, and questions to ask before signing.

Sep 11, 2026

Open Agentic AI Vulnerability Assessment What Changes and What Does Not
Agentic AI Vulnerability Assessment What Changes and What Does Not

Point of View

Agentic AI Vulnerability Assessment What Changes and What Does Not

Agentic AI is expanding what a vulnerability assessment needs to cover, autonomous agents bring their own credentials, tool access, and memory, adding a genuinely new asset class alongside servers and endpoints. It's also compressing attacker timelines and introducing risk categories like goal hijacking and tool misuse that don't map to a traditional CVE. But the core discipline hasn't changed: the same lifecycle of scoping, scanning, prioritizing, and remediating still applies, human judgment still drives prioritization, and accountability still sits with the people who deployed the agent, not the agent itself.

Sep 9, 2026