PACO.IO

Obsidian Vault Portal v2.0
guest@paco.io:~$cat "_posts/2026-11-18-ptir-daily-briefing.md"
18 November 2026

PTIR — Daily Briefing — November 18, 2026

by

Executive Summary

Two developments merit action. Red Hat is running a hands-on Linux hardening workshop today covering SELinux, fapolicyd, and auditd. GitHub has also added opt-in secret scanning to Copilot security review, allowing developers and coding agents to check current changes against GitHub’s secret detectors before merge.

Action Queue

1. Register for today’s Red Hat Linux-hardening workshop

Red Hat’s virtual workshop runs today, November 18, from 1:00–2:30 p.m. Eastern (12:00–1:30 p.m. Central). It introduces three complementary controls: SELinux mandatory access control, fapolicyd application allowlisting and integrity checks, and auditd monitoring and forensic reporting. Lab materials are provided, and the official page says no advance student preparation is required.

Recommended action: Register immediately if the time is still available, then use the session to build a compact hardening checklist that can transfer to Fedora, RHEL, self-hosted systems, or a classroom demonstration.

  • Urgency: Immediate
  • Importance: ★★★★★
  • Verified active: November 18, 2026
  • Deadline: Workshop begins November 18 at 1:00 p.m. Eastern / 12:00 p.m. Central
  • Cost: No fee is listed on the official registration page; no regular price is stated
  • Requirements: Basic Linux familiarity; laptop with Chrome 125+, Firefox 124+, Safari 17.3+, or Edge 125+; registration for virtual access
  • Official registration: Red Hat Linux-hardening workshop

2. Add GitHub secret scanning to one Copilot security-review workflow

GitHub’s public preview adds its secret-scanning detectors to Copilot’s existing security-review specialist. After opt-in, reviews can check added changes against more than 500 provider patterns and a fine-tuned detector for credentials without a recognizable format. It works in Copilot CLI, the Copilot app, SDK integrations, and Copilot code review.

This is a pre-merge check, not a repository-history audit. It is off by default, requires a supported Copilot review workflow, and consumes AI credits under GitHub’s Secret Protection AI Credit SKU.

Recommended action: Enable the feature in one noncritical repository, deliberately test it with a safe dummy credential pattern, and document where the check runs and what it does not cover. Keep existing history scanning and credential-rotation procedures.

  • Urgency: This week
  • Importance: ★★★★☆
  • Verified active: November 18, 2026
  • Deadline: No deadline; public preview
  • Cost: No additional plan is required for users who already have access to Copilot security review or code review; scans consume AI credits
  • Requirements: An eligible Copilot security-review or code-review workflow; explicit opt-in; repository permissions appropriate to the selected integration
  • Official instructions: GitHub Changelog

Linux & Self-Hosting

The Red Hat workshop is useful because it treats Linux hardening as a layered system rather than a single switch: SELinux constrains access, fapolicyd limits executable trust, and auditd records security-relevant activity. The transferable lesson is to combine prevention, allowlisting, and evidence collection—and to test policy changes before applying them to production hosts.

GitHub Discoveries

GitHub’s new scan closes a practical gap in agent-assisted coding: secrets can now be checked inside the same review loop that evaluates generated changes. The limitation matters just as much as the feature: current-change scanning does not replace a full history scan or remediation after a credential has already escaped.

PKb Candidates

Three-layer Linux hardening checklist: Keep a durable note that maps SELinux, fapolicyd, and auditd to control objective, configuration location, verification command, rollback method, and expected failure mode.

Pre-merge secret-detection boundary: Record which tools scan working changes, pull-request additions, and repository history; who receives alerts; how false positives are handled; and when exposed credentials must be rotated rather than merely removed.

tags: linux - cybersecurity - selinux - github - copilot - secret-scanning