Recently active topics

Forward is presenting at Security Field Day 16 this afternoon, and the session is streaming live for anyone to watch. It’s a great session if you’re responsible for exposure management, segmentation, or CVE prioritization at your organization.Register to get the livestream linkWhen: Today, Thursday, October 29, 2:30–4:00 PM PTSpeakers: Brandon Heller, CTO and Co-Founder, and Renata Budko, Senior Director of Product Management, Security and CloudVulnerability scanners sort findings by CVSS severity, and attack surface tools only see what faces the internet. Neither shows you what an attacker can actually reach. In this 90-minute session, the team will show how Forward's network digital twin ranks every critical asset by network exposure, vulnerability severity, and business criticality, giving you one remediation queue in priority order.This session will cover: How exposure, severity, and business criticality combine into a single risk score for each critical asset How transitive expo

Just a quick note here for future reference:Out of the box, Inventory+ shows both physical and virtual firewalls.  For example, a Fortigate with five VDOMs will probably result in 6 inventory items.If you want an inventory of just your hardware devices, you can achieve that by comparing the device.system.physicalName with the device.name.  If there is a difference we can assume that this device is a virtual one running on a physical firewall host.   Here is the code for convenience: /** * @intent Find only physical devices for inventory * @description This script checks to see if the device.system.physicalName is * different to device.name. If there is a difference we can be fairly certain * that this is a virtual device (e.g. virtual firewall on a physical piece of hardware) */foreach device in network.deviceslet isVirtual = isPresent(device.system.physicalName) && device.system.physicalName != device.nameselect { Device: device.name, Type: if isVirtual then "Virtu

A step-by-step guide for building this app from a completely empty SNOW instance — written for someone newer to ServiceNow. Use-Case:When creating change requests in a ticketing system like ServiceNow (SNOW), the data in them is very dependent on the diligence of the user.  This is usually a very manual process and as such it is subject to inaccuracies, incompleteness etc.On the other hand, Forward Networks can know the before and after state of device(s), so it makes sense to wire the two together.  A change ticket in SNOW triggers a diff analysis in Forward for the devices in that ticket.What you're buildingBy the end of this cookbook you'll have a ticketing app where change requests automatically trigger workspace creation in Forward, then get verified against a new network snapshot before the case can be closed. A link to the diff between the two is put into the ticket as evidence of the change and its effects.   The diff contains not just configuration details, but also the device

Hello NQE Enthusiasts,Another challenge. ChallengePassport TaskLet’s assume you are an agent of Customs and Border Protection (CBP) and are working a border crossing from the US into Canada.  Citizens from the US and Canada DO NOT need a passport to cross the border.  Assume for this scenario that all other nationals do require a passport.  Write an NQE query that returns the  people in the list that require a passport, and who they are and where they are from.Input:List of people crossingBob Smith -  USZhang Wei - China Hiromasa Tahara - JapanJessica Northland - CanadaWess Maple - CanadaPeter Volkman - GermanyJeremy Clarkson- UKRachel Riley - UK Scott Ramirez - Spain Gabriel Martin - FranceKazuko Hashigawa - JapanThomas Bouchard - Canada Hint: Use lists (item in list) and ComparisonsContributions: John Schupp