How do I install the Cis Apache24 7.6 skill?

Run npx skillmds@latest add cyberstrikeus/cis-apache24-7-6 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Cis Apache24 7.6 skill do?

Ensure Insecure SSL Renegotiation Is Not Enabled (Manual) It is listed under Coding & Dev Tools on SkillMD.

Is Cis Apache24 7.6 safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cis Apache24 7.6?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cis Apache24 7.6 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cis Apache24 7.6?

cyberstrikeus (@cyberstrikeus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cis Apache24 7.6 by cyberstrikeus — Agent Skill

Name: Cis Apache24 7.6
Author: cyberstrikeus

File contents

Ensure Insecure SSL Renegotiation Is Not Enabled (Manual)

Profile Applicability

Level 1

Description

A man-in-the-middle renegotiation attack was discovered in SSLv3 and TLSv1 in November 2009 (CVE-2009-3555). First, a work around and then a fix was approved as an Internet Standard as RFC 574, Feb 2010. The work around, which removes the renegotiation, is available from OpenSSL as of version 0.9.8l and newer versions. For details: https://www.openssl.org/news/secadv_20091111.txt The SSLInsecureRenegotiation directive was added in Apache 2.2.15, for web servers linked with OpenSSL version 0.9.8m or later, to provide backward compatibility to clients with the older, unpatched SSL implementations.

Rationale

Enabling the SSLInsecureRenegotiation directive leaves the server vulnerable to man-in-the-middle renegotiation attack. Therefore, the SSLInsecureRenegotiation directive should not be enabled.

Audit

Perform the following steps to determine if the recommended state is implemented:

Search the Apache configuration files for the SSLInsecureRenegotiation directive and verify that the directive is either not present or has a value of off.

Remediation

Perform the following to implement the recommended state:

Search the Apache configuration files for the SSLInsecureRenegotiation directive. If the directive is present modify the value to be off. If the directive is not present then no action is required.

SSLInsecureRenegotiation off

Default Value

SSLInsecureRenegotiation off

References

CIS Controls

v8:

4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software
- Uninstall or disable unnecessary services on enterprise assets and software, such as an unused file sharing service, web application module, or service function.

v7:

14.4 Encrypt All Sensitive Information in Transit
- Encrypt all sensitive information in transit.

Profile

Level 1

---name: cis-apache24-7-6description: Ensure Insecure SSL Renegotiation Is Not Enabled (Manual)---# Ensure Insecure SSL Renegotiation Is Not Enabled (Manual)## Profile Applicability- Level 1## DescriptionA man-in-the-middle renegotiation attack was discovered in SSLv3 and TLSv1 in November 2009 (CVE-2009-3555). First, a work around and then a fix was approved as an Internet Standard as RFC 574, Feb 2010. The work around, which removes the renegotiation, is available from OpenSSL as of version 0.9.8l and newer versions. For details: https://www.openssl.org/news/secadv_20091111.txt The `SSLInsecureRenegotiation` directive was added in Apache 2.2.15, for web servers linked with OpenSSL version 0.9.8m or later, to provide backward compatibility to clients with the older, unpatched SSL implementations.## RationaleEnabling the `SSLInsecureRenegotiation` directive leaves the server vulnerable to man-in-the-middle renegotiation attack. Therefore, the `SSLInsecureRenegotiation` directive should not be enabled.## AuditPerform the following steps to determine if the recommended state is implemented:Search the Apache configuration files for the `SSLInsecureRenegotiation` directive and verify that the directive is either not present or has a value of `off`.## RemediationPerform the following to implement the recommended state:Search the Apache configuration files for the `SSLInsecureRenegotiation` directive. If the directive is present modify the value to be off. If the directive is not present then no action is required.```apacheSSLInsecureRenegotiation off```## Default Value```apacheSSLInsecureRenegotiation off```## References1. https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslinsecurerenegotiation2. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2009-35553. https://azure.microsoft.com/en-us/services/multi-factor-authentication/## CIS Controls**v8:**- 4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software - Uninstall or disable unnecessary services on enterprise assets and software, such as an unused file sharing service, web application module, or service function.**v7:**- 14.4 Encrypt All Sensitive Information in Transit - Encrypt all sensitive information in transit.## Profile- Level 1

Frequently asked questions

Cis Apache24 7.6