#Runbook
A Network Outage Runbook for Planned Maintenance Windows

#CMMC #FedRAMP
A Network Outage Runbook for Planned Maintenance Windows
This runbook template guides organizations in managing planned network outages, ensuring mission-critical functions remain operational and compliant with NIST controls.
complydefense.org
November 18, 2026 at 8:05 PM
Migration Runbook Rollback Points for SQL Server Upgrades

Which steps of a SQL Server 2019 to 2025 upgrade can you undo? Tests of backup, attach and compatibility level, and a runbook with a point of no return.
Migration Runbook Rollback Points for SQL Server Upgrades
Which steps of a SQL Server 2019 to 2025 upgrade can you undo? Tests of backup, attach and compatibility level, and a runbook with a point of no return.
www.sqlserverscience.com
November 19, 2026 at 2:06 PM
Nine hours from disclosure to attack—did you log the exact patch window for Alpine in your runbook?
November 15, 2026 at 9:43 PM
3/3 Read the complete production runbook, API routing diagram, and the middle benchmark comparison table here: https://bijaktechnology.com/en/blog/supabase-self-hosted-vs-saas-hemat-biaya-vps/ #CloudEngineering #FinOps #Supabase 3/3
November 18, 2026 at 1:30 PM
A good migration runbook explains how to proceed. An AI-operated one also executes steps, records proof, and pauses at decision points.
November 18, 2026 at 4:11 PM
Automating runbook steps is half the win; the other half is making the post-incident report write itself from the same data.
November 18, 2026 at 6:16 AM
Migration Runbook Rollback Points for SQL Server Upgrades

Which steps of a SQL Server 2019 to 2025 upgrade can you undo? Tests of backup, attach and compatibility level, and a runbook with a point of no return.

www.sqlserverscience.com/maintenance/…
Migration Runbook Rollback Points for SQL Server Upgrades
You’re writing the change request for a move from SQL Server 2019 to SQL Server 2025, and you reach the rollback section. The obvious line is “restore the pre-upgrade backup on the old server.” That works until the new server has taken writes you can’t afford to lose. Some parts of the upgrade can’t be reversed at all. I wanted each rollback step in my runbook to rest on something I had tested, so I tested the directions that matter on two local instances. This post covers what can and can’t go back, and ends with the runbook I’d use. The planning work before this point is in Migration Planning: Compatibility Checks and Deprecated Features, and the checks after it are in Post-Migration Validation with AI-Generated Test Scripts. ## The Test Setup I used two instances on one workstation: SQL Server 2019 (15.0.4500.2, Developer) and SQL Server 2025 (17.0.5015.4, Enterprise Developer). Each test used a small scratch database with one table, `[dbo].[orders]`, and a few rows that record where each row was written. I tracked two different version numbers. The compatibility level is a per-database setting that controls query processing and some Transact-SQL behaviour.[1] The other is the value `DATABASEPROPERTYEX(name, 'Version')` returns. Microsoft Learn describes it as the internal version number of the SQL Server code with which the database was created, says it returns NULL when the database hasn’t started, and marks it as informational only and not supported.[2] What I saw doesn’t fit that description well. A 2019 database restored on 2025 reported 904 while it sat in `RESTORING`, and 998 after the upgrade. I used the property here because the number changed at the point the upgrade ran. Transact-SQL USE [master]; SELECT [d].[name] , [d].[state_desc] , [d].[compatibility_level] , DATABASEPROPERTYEX([d].[name], 'Version') AS [internal_version] FROM [sys].[databases] AS [d] WHERE [d].[name] LIKE N'sat[_]mig%'; 1234567891011 | USE [master]; SELECT [d].[name] , [d].[state_desc] , [d].[compatibility_level] , DATABASEPROPERTYEX([d].[name], 'Version') AS [internal_version]FROM [sys].[databases] AS [d]WHERE [d].[name] LIKE N'sat[_]mig%'; ---|--- A new database on the 2025 instance reported internal version 998 and compatibility level 170. A new database on the 2019 instance reported internal version 904 and compatibility level 130. It got 130 because `model` on that instance is at 130, and new databases take the lower of the engine default and the `model` level.[1] ## A 2025 Backup Doesn’t Restore on 2019 I backed up the 2025 database and tried to restore it on 2019. `RESTORE HEADERONLY` on the 2019 instance read the file without complaint. It returned `DatabaseVersion` 998, `SoftwareVersionMajor` 17 and `CompatibilityLevel` 170, so you can inspect a newer backup from an older server. Proving the Restore, Part 2: HEADERONLY Changes Shape Between Versions covers how that output differs between versions. The restore itself failed: Msg 3169, Level 16, State 1, Server SQLWS01\SQL2019, Line 1 The database was backed up on a server running version 17.00.5015. That version is incompatible with this server, which is running version 15.00.4500. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. Msg 3013, Level 16, State 1, Server SQLWS01\SQL2019, Line 1 RESTORE DATABASE is terminating abnormally. 1234 | Msg 3169, Level 16, State 1, Server SQLWS01\SQL2019, Line 1The database was backed up on a server running version 17.00.5015. That version is incompatible with this server, which is running version 15.00.4500. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.Msg 3013, Level 16, State 1, Server SQLWS01\SQL2019, Line 1RESTORE DATABASE is terminating abnormally. ---|--- No database was created. This matches the documentation, which says SQL Server backups can’t be restored by any earlier version.[3] That backup was at level 170, which 2019 doesn’t support. To see whether a lower level changes the result, I created a second database on 2025, set it to compatibility level 130, which 2019 does support,[1] and backed it up. On 2019, `RESTORE HEADERONLY` reported `CompatibilityLevel` 130 and `DatabaseVersion` 998. The restore failed with the same Msg 3169 and Msg 3013, and no database was created. The error names the server version, and the lower level made no difference. ## A 2019 Backup Restores on 2025, and the Database Is Upgraded The forward direction works. I put the 2019 database in the full recovery model, took a full backup, inserted a second row and took a log backup. On 2025 I restored the full backup `WITH NORECOVERY`, which is how log shipping seeds a secondary: Transact-SQL USE [master]; RESTORE DATABASE [sat_mig_runbook_up] FROM DISK = N'C:\backup\sat_mig_runbook_2019.bak' WITH MOVE N'sat_mig_runbook' TO N'D:\data\sat_mig_runbook_up.mdf' , MOVE N'sat_mig_runbook_log' TO N'L:\log\sat_mig_runbook_up_log.ldf' , NORECOVERY; RESTORE LOG [sat_mig_runbook_up] FROM DISK = N'C:\backup\sat_mig_runbook_2019.trn' WITH RECOVERY; 123456789101112 | USE [master]; RESTORE DATABASE [sat_mig_runbook_up] FROM DISK = N'C:\backup\sat_mig_runbook_2019.bak' WITH MOVE N'sat_mig_runbook' TO N'D:\data\sat_mig_runbook_up.mdf' , MOVE N'sat_mig_runbook_log' TO N'L:\log\sat_mig_runbook_up_log.ldf' , NORECOVERY; RESTORE LOG [sat_mig_runbook_up] FROM DISK = N'C:\backup\sat_mig_runbook_2019.trn' WITH RECOVERY; ---|--- While the database sat in `RESTORING`, it still reported internal version 904. That matches Microsoft’s log shipping upgrade article, which says a secondary database isn’t upgraded until it’s brought online.[4] The upgrade ran when the log restore brought it online: Processed 0 pages for database 'sat_mig_runbook_up', file 'sat_mig_runbook' on file 1. Processed 4 pages for database 'sat_mig_runbook_up', file 'sat_mig_runbook_log' on file 1. Converting database 'sat_mig_runbook_up' from version 904 to the current version 998. Database 'sat_mig_runbook_up' running the upgrade step from version 904 to version 905. Database 'sat_mig_runbook_up' running the upgrade step from version 905 to version 906. [... 87 more upgrade-step lines removed for this post ...] Database 'sat_mig_runbook_up' running the upgrade step from version 997 to version 998. RESTORE LOG successfully processed 4 pages in 0.002 seconds (13.671 MB/sec). 12345678 | Processed 0 pages for database 'sat_mig_runbook_up', file 'sat_mig_runbook' on file 1.Processed 4 pages for database 'sat_mig_runbook_up', file 'sat_mig_runbook_log' on file 1.Converting database 'sat_mig_runbook_up' from version 904 to the current version 998.Database 'sat_mig_runbook_up' running the upgrade step from version 904 to version 905.Database 'sat_mig_runbook_up' running the upgrade step from version 905 to version 906.[... 87 more upgrade-step lines removed for this post ...]Database 'sat_mig_runbook_up' running the upgrade step from version 997 to version 998.RESTORE LOG successfully processed 4 pages in 0.002 seconds (13.671 MB/sec). ---|--- Afterward the database was `ONLINE` at internal version 998, with both rows present. Its compatibility level stayed at 130. Microsoft documents that a restored or attached database keeps its compatibility level if the new instance supports it.[1] So the 2025 copy can’t go back to 2019 as a backup, and the only restore point is the 2019 database or a backup taken there. Anything written on 2025 after cutover isn’t in that copy. If you need those rows after a rollback, you have to plan how to carry them back. ## Detach and Attach Go One Way Too I created another scratch database on 2025 and detached it. I copied its files to the 2019 data folder, then attached the original files back on 2025. Attaching the copies on 2019 failed: Msg 1813, Level 16, State 2, Server SQLWS01\SQL2019, Line 3 Could not open new database 'sat_mig_attach'. CREATE DATABASE is aborted. Msg 948, Level 20, State 1, Server SQLWS01\SQL2019, Line 3 The database 'sat_mig_attach' cannot be opened because it is version 998. This server supports version 904 and earlier. A downgrade path is not supported. 1234 | Msg 1813, Level 16, State 2, Server SQLWS01\SQL2019, Line 3Could not open new database 'sat_mig_attach'. CREATE DATABASE is aborted.Msg 948, Level 20, State 1, Server SQLWS01\SQL2019, Line 3The database 'sat_mig_attach' cannot be opened because it is version 998. This server supports version 904 and earlier. A downgrade path is not supported. ---|--- Error 948 is severity 20, and it closed my connection. Microsoft lists severities 20 to 24 as fatal errors and says the application’s connection might also end.[5] Microsoft’s detach and attach article says an attached database is upgraded when it’s attached, which prevents its use with an older version of the Database Engine.[6] If you plan to move files rather than backups, keep a copy of the 2019 files that was never attached anywhere newer. ## Compatibility Level Is the Part You Can Reverse On the upgraded copy, I raised the compatibility level, lowered it part way, and then set it back to 130, where it started: Transact-SQL USE [master]; ALTER DATABASE [sat_mig_runbook_up] SET COMPATIBILITY_LEVEL = 170; ALTER DATABASE [sat_mig_runbook_up] SET COMPATIBILITY_LEVEL = 150; ALTER DATABASE [sat_mig_runbook_up] SET COMPATIBILITY_LEVEL = 130; 12345 | USE [master]; ALTER DATABASE [sat_mig_runbook_up] SET COMPATIBILITY_LEVEL = 170;ALTER DATABASE [sat_mig_runbook_up] SET COMPATIBILITY_LEVEL = 150;ALTER DATABASE [sat_mig_runbook_up] SET COMPATIBILITY_LEVEL = 130; ---|--- Step | Compatibility level | Internal version ---|---|--- After restore on 2025 | 130 | 998 After `SET COMPATIBILITY_LEVEL = 170` | 170 | 998 After `SET COMPATIBILITY_LEVEL = 150` | 150 | 998 After `SET COMPATIBILITY_LEVEL = 130` | 130 | 998 All three changes ran without error, and the two rows were still there at the end. SQL Server 2025 accepts levels 100 through 170.[1] The internal version stayed at 998 the whole time. Lowering the level can undo a plan regression caused by the new level. It doesn’t make the database restorable on 2019. The step is also only mostly reversible. Some enhancements are available only at a higher level,[1] so code written after the change that needs the new level may stop working when the level goes back down. The same article notes that changing the level invalidates the plan cache for that database, so expect recompiles after each change.[1] Upgrading Database Compatibility Levels Across a Whole Instance covers when and how to raise the level. ## Backing Out Before Cutover At cutover, a tail-log backup `WITH NORECOVERY` captures the last log records and leaves the source in `RESTORING`, so nothing else can write to it.[7] I tested the rollback for that step on 2019. I inserted a third row, took the tail-log backup, and then brought the source back: Transact-SQL USE [master]; BACKUP LOG [sat_mig_runbook] TO DISK = N'C:\backup\sat_mig_runbook_2019_tail.trn' WITH INIT, CHECKSUM, NORECOVERY; RESTORE DATABASE [sat_mig_runbook] WITH RECOVERY; 1234567 | USE [master]; BACKUP LOG [sat_mig_runbook] TO DISK = N'C:\backup\sat_mig_runbook_2019_tail.trn' WITH INIT, CHECKSUM, NORECOVERY; RESTORE DATABASE [sat_mig_runbook] WITH RECOVERY; ---|--- The database went from `RESTORING` back to `ONLINE`, with all three rows. Until applications write to the new server, this is the whole rollback: bring the source online and point the applications back at it. ## Keeping a Path Back After Cutover I didn’t test any of these, so the following comes from Microsoft Learn. * **Log shipping** can’t go from a newer version to an older one. The log shipping upgrade article says a backup made on a newer version can’t be restored on an older one, which is why secondaries must be upgraded before the primary.[4] * **Availability groups** behave the same way. An upgraded primary can’t ship logs to a secondary that’s still on the older version.[8] After you fail over to a 2025 replica, the 2019 replicas stop receiving changes. * **Transactional replication** can run from new to old. The compatibility matrix lists SQL Server 2019 as a supported subscriber for a SQL Server 2025 publisher, and the distributor has to be on 2025 as well.[9] It’s a separate system to set up, monitor and test before cutover. * **Exporting changed rows** from the new server and loading them into the old one is possible if the application tracks change dates. That’s application work, and it needs a test before cutover. * **Accepting the loss** is the last option. Sometimes the answer is “we accept the loss.” If so, I want that signed before the window opens, along with how long the 2019 copy stays available. ## The Runbook This is the order I’d follow. Every step above the marked line can be undone by bringing the 2019 database back online. 1. Run the compatibility and deprecated feature checks from the planning post. Record each database’s current compatibility level. 2. Build the 2025 instance. Migrate logins with their SIDs, plus Agent jobs, linked servers and server settings. 3. Take a full backup on 2019 `WITH CHECKSUM`. Restore it on 2019 under a different name to prove it restores. This is the rollback copy. 4. Seed 2025 by restoring that full backup `WITH NORECOVERY`, and keep applying log backups from 2019. 5. Rehearse: restore a copy `WITH RECOVERY` on a test instance, run the validation scripts, and time the upgrade steps. 6. Stop application writes on 2019. Take the tail-log backup `WITH NORECOVERY`. 7. Restore the tail log on 2025 `WITH RECOVERY`. The database upgrades here. The 2019 source is still intact in `RESTORING`. 8. Leave the compatibility level where it was. Run the post-migration validation against 2025 before you open it to applications. 9. Decide go or no-go. For no-go, run `RESTORE DATABASE ... WITH RECOVERY` on 2019 and point the applications back. **Point of no return:** the applications start writing to SQL Server 2025. After that line: * Rolling back to 2019 means losing every write made on 2025, unless you set up one of the options above. Leave the 2019 database in `RESTORING`, and keep its final backups, for the agreed period. * Raise the compatibility level later, as its own change. If plans regress, set the level back. That step is mostly reversible on 2025, but code written to need the new level may not work after the level goes back down. ## Limits of This Test I tested one build of each version, on one workstation, with tiny databases. The upgrade on a large database may take longer, and a database from an older version may run more upgrade steps. I didn’t test log shipping, availability groups, replication or Managed Instance. The section on those relies on Microsoft Learn. I also didn’t test databases that use TDE, FILESTREAM or In-Memory OLTP. Related: Azure SQL Managed Instance Differences That Catch DBAs During a Migration. If your runbook has a rollback step I haven’t covered here, or you’ve used replication back to the old version after an upgrade, I’d like to hear how it went. Find me on Bluesky or LinkedIn. ## References 1. ALTER DATABASE Compatibility Level (Transact-SQL) - Microsoft Learn. Lists the supported levels per version, states that new databases take the lower of the default and the model level, that restored or attached databases keep a supported level, and that changing the level invalidates the plan cache. ↩ 2. DATABASEPROPERTYEX (Transact-SQL) - Microsoft Learn. Describes the Version property as an internal version number, informational only and not supported. ↩ 3. Copy Databases with Backup and Restore - Microsoft Learn. States that SQL Server backups can’t be restored by any earlier version of SQL Server. ↩ 4. Upgrade SQL Server Log Shipping - Microsoft Learn. Says to upgrade secondaries before the primary, because a backup created on a newer version can’t be restored on an older version. ↩ 5. Database Engine Error Severities - Microsoft Learn. Describes severities 20 to 24 as fatal errors and says the application connection to the Database Engine might also terminate. ↩ 6. Upgrade a database using detach and attach (Transact-SQL) - Microsoft Learn. States that an attached database is upgraded automatically, which prevents its use with an older version of the Database Engine. ↩ 7. Tail-log backups (SQL Server) - Microsoft Learn. States that a tail-log backup with NORECOVERY takes the database into the restoring state, which guarantees that the database doesn’t change after the backup. ↩ 8. Upgrade Availability Group Replicas - Microsoft Learn. States that an upgraded primary replica can no longer ship logs to a secondary replica that hasn’t been upgraded to the same version. ↩ 9. Replication backward compatibility - Microsoft Learn. The transactional replication matrix, which lists SQL Server 2019 as a supported subscriber for a SQL Server 2025 publisher and SQL Server 2025 as the only supported distributor for that publisher. ↩ ### Share this: * Share on LinkedIn (Opens in new window) LinkedIn * Share on Bluesky (Opens in new window) Bluesky * Share on Mastodon (Opens in new window) Mastodon * Email a link to a friend (Opens in new window) Email * More * * Share on Threads (Opens in new window) Threads * Share on Reddit (Opens in new window) Reddit * Share on Facebook (Opens in new window) Facebook * Share on WhatsApp (Opens in new window) WhatsApp * Print (Opens in new window) Print * ### Like this: Like Loading… ### _Related_
www.sqlserverscience.com
November 19, 2026 at 2:07 PM
Serving the runbook MCP server over streamable HTTP with OAuth, then using it as a claude.ai custom connector and through the Messages API from Go.
#ai #llm #go #claude #mcp
https://stdout.adegoodyer.com/posts/remote-mcp-servers-and-connectors/?utm_source=bluesky
Building With Claude: Part 8 - Remote MCP Servers and Connectors
Serving the runbook MCP server over streamable HTTP with OAuth, then using it as a claude.ai custom connector and through the Messages API from Go.
stdout.adegoodyer.com
November 15, 2026 at 12:15 PM
Case PROVE-IT-0x88ECA5. 180 started. The forger: still undefeated. 😏

7 signed reports, 1 key runbook, 3,300+ CloudTrail events. Free to play.
https://proveit.alfanestlabs.com/?utm_source=bluesky&utm_medium=social&utm_campaign=20261118-17-proveit
November 18, 2026 at 4:01 PM
Find it. Design it. Build it. Hand it over.

Name the one workflow slowing you down. Lock the steps, your existing systems and the success number. Connect, test and train on tools you already run. Switch over with a rollback plan and a runbook.

stravynt.com
November 17, 2026 at 5:29 PM
The runbook says to check the logs, which is not narrowing it down.
November 11, 2026 at 10:42 PM
Yeah there's probably a runbook in someone's head for this.

The status updates are not encouraging.
November 13, 2026 at 4:42 AM
Blocking access through a gateway does not necessarily end every process running on the platform that hosts the agent.

That can be the right control. Just know which one you have. In your runbook, "disable the agent" should list what actually stops and what keeps running.
November 15, 2026 at 8:30 PM
Still on HCL Domino 10.x or 11.x? Prominic usually sees one of three reasons for this: a custom app nobody wants to touch, an admin who left without a runbook, or a renewal that just keeps stretching.

buff.ly/NlJUPJg
November 18, 2026 at 5:08 PM
Django vận hành production #20: Tổng kết series — runbook vận hành, checklist xử lý sự cố, hướng phát triển tiếp

Tập cuối khép lại hành trình đưa ứng dụng quản lý chi tiêu lên production: bạn sẽ có một runbook vận hành hoàn chỉnh, một checklist xử lý sự cố dùng được ngay trong ca trực, và lộ trình…
Django vận hành production #20: Tổng kết series — runbook vận hành, checklist xử lý sự cố, hướng phát triển tiếp
Tập cuối khép lại hành trình đưa ứng dụng quản lý chi tiêu lên production: bạn sẽ có một runbook vận hành hoàn chỉnh, một checklist xử lý sự cố dùng được ngay trong ca trực, và lộ trình nâng cấp tiếp theo. Nối tiếp tập 19 về mở rộng nhiều worker và read replica, tập này gom toàn bộ series thành một quy trình vận hành bền vững.
linhfish.dev
November 16, 2026 at 1:16 PM
A 200-page runbook guarantees ambiguity only until the first person edits it in 2027. Drift is a feature, not a bug.
November 15, 2026 at 12:29 AM
📝 Who's On Call for the AI Agent? A Production Runbook

An agent that can call production tools is a service with an incident path, not a clever prompt.

Read here: https://devops-daily.com/posts/who-is-on-call-for-the-ai-agent
devops-daily.com
November 17, 2026 at 8:00 AM
Look at you and your fancy pants complicated runbook! I think they had a guy like that. He probably got fired last week to increase operational efficiencies.
November 13, 2026 at 6:23 AM
The IT Side of a Pen Test Week, a Client-Side Runbook
A pen tester at a company of 30 to 80 people usually works for 3 to 5 days, and the prep around those days takes closer to 4 weeks. This is the runbook I use from the client side for the IT part of that month, written for whoever on staff ends up owning it. Defending against the tester isn't on the list. What is on it is knowing which traffic is theirs, not changing the network mid-test, having someone who can stop things, and protecting the old servers that can't take much load. The problem The report you pay for describes one week of your network. Push a firewall change on day 2, or let the tester get blocked on day 1, and it ends up describing a week that didn't really happen, which nobody on your side can do much with. NIST SP 800-115 calls planning the first phase of a security test (it comes before any testing traffic is sent), and in my experience nearly all of the planning below lands on IT. 1. Get the tester's source addresses into the scope letter Along with the systems in scope by IP address, domain and application, the dates and hours, and banned actions such as denial of service or copying real customer records, the scope letter we use lists the addresses the tester will work from. That last item is for the logs. After the test I go through the client's firewall logs with that address list next to them, and anything from those addresses is the tester's, while anything else that hit the edge that week gets looked at on its own. Without the list we'd be going back and forth on every odd connection. 2. Decide what your monitoring provider is told I don't think there's a clean answer here, and the options I weigh with clients look like this. Tell nobody at the provider, and you find out whether they'd have caught a real intruder. Tell their whole analyst team, and the test stops telling you anything about detection. Tell nobody and get blocked the morning of day 1, and on a 5-day test that's 20% of what you paid for gone. My compromise is one senior person at the provider who knows, and nobody on their analyst floor. If you use (or are about to sign with) a managed detection and response provider, ask before signing how they'd treat alerts from the tester's addresses. As for your own staff, the CIS Controls v8.1 guidance on penetration testing says only a few people in an organization should know, with one person named as the main contact if something goes wrong. On my projects that's the owner, the IT lead, and whichever manager has a team that might notice odd logins (plus HR, in writing, before the first phishing email is sent if phishing is in scope). 3. Patch the edge before the tester arrives CISA added 321 entries to its Known Exploited Vulnerabilities catalog between November 17, 2025 and November 13, 2026. Of those, 64 were in firewall and remote access products from makers like Cisco, Fortinet, Ivanti, SonicWall and Citrix, and Microsoft products accounted for another 42. Since that's the gear attackers go after first, it's also the gear my clients patch first. On our countdown that happens 10 days before kickoff. Check those entries against your own firewall, VPN and Microsoft products, update firmware, turn on MFA for every admin and remote access account, change default passwords, and leave the rest alone. I know some prep guides say to fix everything first. I don't agree, since then you're paying a tester to confirm your scan results. The snag I see on this step is a firmware update needing a maintenance window nobody booked, so I ask for that window to be booked when the letter is signed. 4. Protect the fragile machines Windows Server 2012 R2 is the usual one. Extended support ended in October 2023 and the last paid security update year ended October 14, 2026, and I still find those machines in Dallas server closets running payroll or a line-of-business database. They go into the scope letter with a note to test gently or skip them, along with anything else that can't take much load. The day before testing, take a fresh backup of them. A week out (day 7 on our countdown), do one real restore of a file share or virtual machine and write down how long it took. CISA's #StopRansomware Guide says to test backup procedures regularly anyway, and a console that says "success" hasn't shown you the data comes back. 5. Staff the window I want 2 names and 2 cell numbers on the client side for the test window. One of them can call a pause, and the other can restart a server in the evening if one goes down. You don't need a security analyst for this. BLS counts 7,080 information security analysts in the Dallas-Fort Worth metro in May 2025 at a mean of $133,790 a year, and a 60-person company can't usually carry that salary, so the 2 names on my contact sheet tend to be someone from the IT provider and the office manager or controller. There's a stop word as well, and testing stops when anyone says it. The letter also says what happens if the tester sees signs of a real attacker. In ours, testing pauses and the tester calls the named contact before doing anything else. 6. Freeze changes Hold off on nonurgent changes for the week. A firewall rule somebody pushes on Wednesday can leave Thursday's results unreadable, since then you can't say which configuration the tester saw. 7. Handle the report like a credential CIS warns the report can work as step-by-step directions for breaking in. I keep copies to the 2 or 3 people doing the fixes, and one goes in the client's security records. When testing ends on a Friday, the readout call goes on the calendar for the next week, 2 or 3 days of IT time get blocked right after it for the critical findings, and a retest is set about 30 days out. Gotchas On the countdown I send Dallas clients about a month out, these are the snags that come up at the IT steps. Staffing (step 9 on the full countdown) goes wrong when the only admin has vacation booked that week. On step 6 it's a firmware update that needs a maintenance window nobody booked. At step 8 the SOC blocks the tester on day 1, and the test stalls. For step 7, a backup job that reports success turns out never to have been restored. And at step 10 the report lands, then sits in an inbox for a quarter. Takeaway Looking back over that list, very little of it is security work in the usual sense. It's logistics, and when it's done the report you get back should describe the network you actually run rather than a week of blocked traffic and half-made changes. The full 10-step version, including the Texas law behind the scope letter and vendor approvals, is in our guide on how to prepare for a penetration test in Dallas.
dev.to
November 17, 2026 at 10:43 AM
unlocking the Door of Time should have been a big event with dignitaries and security details and a whole runbook procedure to follow, but instead it's just some kid turning knobs until the nuclear missile detonates in its silo and takes out the whole city
November 12, 2026 at 4:57 PM
The part worth planning for isn't the installer, it's the .NET 11 base - per the PowerShell team's 7.7 GA post that's what it's built on. I'd test automation pipelines and runbook images before swapping anything in; binary modules would be my first suspect, though that part is untested.
November 17, 2026 at 3:03 AM
🚨 EUVD-2026-126267
📊 6.1/10
🏢 Octopus Deploy

📝 In affected versions of Octopus Server, improper path validation allowed a user with scoped runbook permissions to execute runbooks on offline pa...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-126267

#cybersecurity #infosec #cve #euvd
November 16, 2026 at 1:04 PM