[et_pb_section fb_built=”1″ admin_label=”Template Basic Section” _builder_version=”4.16″ global_colors_info=”{}”][et_pb_row admin_label=”Header Row” _builder_version=”4.27.4″ _module_preset=”default” collapsed=”off” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_image src=”https://mitchellberg.com/wp/wp-content/uploads/2025/02/banner_portfolio.png” alt=”My Portfolio” title_text=”banner_portfolio” admin_label=”Header Image” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][/et_pb_image][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
[/et_pb_text][et_pb_text admin_label=”Expository Text” _builder_version=”4.27.4″ _module_preset=”default” custom_padding=”0px|||||” global_colors_info=”{}”]
More Patch for Neurons
I’ll add, and explain, some other collateral from Patch for Neurons here.
Our perspective in designing the system, proved out through user research, was that different users would approach Patching from different perspectives: software, hardware, compliance and history/event logging. Each area has an entry point, below.
[/et_pb_text][et_pb_divider _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][/et_pb_divider][/et_pb_column][/et_pb_row][et_pb_row column_structure=”3_5,2_5″ admin_label=”Patch Intel Row” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”3_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text admin_label=”PI Text” _builder_version=”4.27.4″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”]
Patch Intelligence
Patch intelligence is essentially a software research tool, allowing the user to connect “advisories” and bulletins about vulnerabilities to content (patches) available from software vendors. The user could then test the content on their environment (using Ring Deployment), go through change management, or whatever their organization and process call for.
[/et_pb_text][/et_pb_column][et_pb_column type=”2_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_image src=”https://mitchellberg.com/wp/wp-content/uploads/2025/02/patch_intelligence_-_sync_individual_patch.png” alt=”Patch Intelligence page” title_text=”patch_intelligence_-_sync_individual_patch” show_in_lightbox=”on” admin_label=”PI Image” _builder_version=”4.27.4″ _module_preset=”default” border_radii=”on|1px|1px|1px|1px” global_colors_info=”{}”][/et_pb_image][et_pb_text admin_label=”PI Caption” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
The Patch Intelligence page. It links industry bulletins and announcements to vendor content, and also includes “reliability” information gleaned from industry social media chatter about the patch.
[/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row admin_label=”Divider Row” _builder_version=”4.27.4″ _module_preset=”default” collapsed=”on” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_divider _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][/et_pb_divider][/et_pb_column][/et_pb_row][et_pb_row column_structure=”3_5,2_5″ admin_label=”EPV Row” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”3_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text admin_label=”EPV Text” _builder_version=”4.27.4″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”]
Endpoint Vulnerability
This is a list of the system’s endpoints – computers.
It shows a wealth of information about the patching state, process status and identity of each machine.
The active filtering widgets at the top of the page allow the user to home in on the machines of greatest interest – unpatched machines, machines with active exploits or unpatched vulnerabilities, as well as construct and save their own filter criteria.
[/et_pb_text][/et_pb_column][et_pb_column type=”2_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_image src=”https://mitchellberg.com/wp/wp-content/uploads/2025/02/epv_with_rings.png” alt=”Endpoint Vulnerability Page, Final” title_text=”epv_with_rings” show_in_lightbox=”on” admin_label=”EPV Image” _builder_version=”4.27.4″ _module_preset=”default” border_radii=”on|1px|1px|1px|1px” global_colors_info=”{}”][/et_pb_image][et_pb_text admin_label=”EPV Caption” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
The Endpoint Vulnerability page. This shows information about “endpoints” – computers on the network; patching status, “risk” (the level of current patches not applied) and the status of any processes on each endpoint.
[/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row admin_label=”Divider Row” _builder_version=”4.27.4″ _module_preset=”default” collapsed=”on” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_divider _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][/et_pb_divider][/et_pb_column][/et_pb_row][et_pb_row column_structure=”3_5,2_5″ admin_label=”Deploy History Row” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”3_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text admin_label=”DH Text” _builder_version=”4.27.4″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”]
Deployment History
This is a glorified event log, chronicling every event that relates to patching. All of them.
The active widgets at the top allow the user to re-filter the page below into more useful segments; there is also column filtering to further segment the data, and the ability to save and re-apply sets of filtering criterial.
[/et_pb_text][/et_pb_column][et_pb_column type=”2_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_image src=”https://mitchellberg.com/wp/wp-content/uploads/2025/02/deployment_history__bak_.png” alt=”Deployment History page” title_text=”deployment_history__bak_” show_in_lightbox=”on” admin_label=”DH Image” _builder_version=”4.27.4″ _module_preset=”default” border_radii=”on|1px|1px|1px|1px” global_colors_info=”{}”][/et_pb_image][et_pb_text admin_label=”DH Caption” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
Figure 1 – one of our design iterations. It was not a successful one – it was no advance over the on-premises version. It took minutes to design, andseconds to dispose of.
[/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row admin_label=”Divider Row” _builder_version=”4.27.4″ _module_preset=”default” collapsed=”on” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_divider _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][/et_pb_divider][/et_pb_column][/et_pb_row][et_pb_row column_structure=”3_5,2_5″ admin_label=”Patch Settings Row” _builder_version=”4.27.4″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”3_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text admin_label=”PSC Text” _builder_version=”4.27.4″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”]
Actions
Patch Settings Configuration is where the user automates and systematizes patching the environment: setting policies that get pushed out to the agents on the endpoints, setting times and policies for rebooting machines (the most destructive and annoying part of patching), scheduling patching, configuring “Rings” for testing content with test, early adopter and production groups, and much more.
As more and more features accreted into Patching over the. years, a page that had started out relatively simple got, not so much “complex” as very, very long. We started a redesign effort; see more here.
[/et_pb_text][/et_pb_column][et_pb_column type=”2_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_image src=”https://mitchellberg.com/wp/wp-content/uploads/2025/02/deployment_behavior_-_grid__backup__disposable_.png” alt=”Patch Settings Configuration” title_text=”deployment_behavior_-_grid__backup__disposable_” show_in_lightbox=”on” admin_label=”PSC Image” _builder_version=”4.27.4″ _module_preset=”default” border_radii=”on|1px|1px|1px|1px” global_colors_info=”{}”][/et_pb_image][et_pb_text admin_label=”PSC Caption” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
The Patch Settings Configuration page. It’s big and ugly. Check out the notes for the proposed redesign.
[/et_pb_text][et_pb_text admin_label=”%22See Also%22 hed” _builder_version=”4.27.4″ _module_preset=”default” text_font=”|600|||||||” background_color=”rgba(0,0,0,0.1)” text_orientation=”center” border_radii=”on|1px|1px|1px|1px” global_colors_info=”{}”]
See more about the redesig of Patch Settings
[/et_pb_text][/et_pb_column][/et_pb_row][et_pb_row admin_label=”Divider Row” _builder_version=”4.27.4″ _module_preset=”default” collapsed=”on” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_divider _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][/et_pb_divider][/et_pb_column][/et_pb_row][et_pb_row column_structure=”3_5,2_5″ admin_label=”Compliance Row” _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”3_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text admin_label=”CR Text” _builder_version=”4.27.4″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”]
Compliance Reporting
Compliance Reporting wasn’t part of the plan. It came to us during a round of usability testing. It led to some Gartner chatter, and one or two patents.
[/et_pb_text][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
[/et_pb_text][/et_pb_column][et_pb_column type=”2_5″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_image src=”https://mitchellberg.com/wp/wp-content/uploads/2025/02/Compliance-Report-1.png” alt=”Compliance Report” title_text=”Compliance Report” show_in_lightbox=”on” admin_label=”CR Image” _builder_version=”4.27.4″ _module_preset=”default” border_radii=”on|1px|1px|1px|1px” global_colors_info=”{}”][/et_pb_image][et_pb_text admin_label=”Caption” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
A Compliance Report – measuring the patching state against service level agreement over time.
[/et_pb_text][et_pb_text admin_label=”%22See Also%22 hed” _builder_version=”4.27.4″ _module_preset=”default” text_font=”|600|||||||” background_color=”rgba(0,0,0,0.1)” text_orientation=”center” border_radii=”on|1px|1px|1px|1px” global_colors_info=”{}”]
See more about Compliance Reporting
[/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section][et_pb_section fb_built=”1″ admin_label=”Footer Section” _builder_version=”4.27.4″ _module_preset=”default” background_color=”rgba(12,113,195,0.15)” global_colors_info=”{}”][et_pb_row column_structure=”1_5,1_5,1_5,1_5,1_5″ admin_label=”Footer Row” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”1_5″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text admin_label=”Home Text” _builder_version=”4.27.4″ _dynamic_attributes=”link_option_url” _module_preset=”default” link_option_url=”@ET-DC@eyJkeW5hbWljIjp0cnVlLCJjb250ZW50IjoicG9zdF9saW5rX3VybF9wYWdlIiwic2V0dGluZ3MiOnsicG9zdF9pZCI6IjE2MCJ9fQ==@” global_colors_info=”{}”]
Home
Back to the top
[Home]
[/et_pb_text][/et_pb_column][et_pb_column type=”1_5″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text admin_label=”WID Text” _builder_version=”4.27.4″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]
What I Do
All about the things I do and how I do them, and what I’ve achieved so far.
[/et_pb_text][/et_pb_column][et_pb_column type=”1_5″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text admin_label=”Portfolio Text” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
Portfolio
Links to illustrations and case studies of several important projects. (You’ll need to contact me for a password)
[/et_pb_text][/et_pb_column][et_pb_column type=”1_5″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text admin_label=”Resume Text” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
Resume
My most current resume.
[Resume]
[/et_pb_text][/et_pb_column][et_pb_column type=”1_5″ _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text admin_label=”Contact Text” _builder_version=”4.27.4″ _module_preset=”default” global_colors_info=”{}”]
Contact Me
How to reach Mitch Berg
[Contact]]
[/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section]