SCPI (Standard Commands for Programmable Instruments) is a a standard with particular relevance for OpenTAP and the ecosystem of instruments that it supports. SCPI defines an interface for controlling test and measurement devices. Introduced in 1990 as a layer on top of IEEE 488.2-1987, it provides commands for oscilloscopes, multimeters, spectrum analyzers, and power supplies.
An OSPO or Open Source Program Office is a centralized team or department within an organization that manages open source strategy, policies, and practices. The concept of an OSPO has become increasingly popular as more companies recognize the importance of open source in software development and IT in general.
Modern products and services are highly dependent upon the development and application of standards. Without the presence of and adherence to standards, software and systems could not interoperate – every piece of technology, down to basic nuts and bolts and nails used in construction, would be artisanal, raising costs and limiting utility.
In response to the increasing pace of major breaches, ransomeware attacks, network outages and wide-reaching system and application crashes, Government regulators are acting to safeguard individual citizens and businesses. Opinions differ as to the actual impact of open source on security and uptime, but no one would argue that improving the quality and security of all code benefits users, integrators and developers.
Every year for the last four, Keysight has collaborated with faculty at the University of California Santa Cruz (UCSC) Baskin Engineering School to sponsor senior projects in test automation. This year, one of those projects focused on leveraging LLMs (Large Language Models) to improve the timeliness of responses to questions on the OpenTAP Forum.
Wireless network security testing involves evaluating the security measures and protocols of a wireless network to identify vulnerabilities and ensure the network is protected against unauthorized access and attacks. The testing process typically includes several steps and techniques, and so benefit greatly from test automation with OpenTAP
Every year for the last four, Keysight has collaborated with faculty at the University of California Santa Cruz (UCSC) Baskin Engineering School to sponsor senior projects in test automation. This year (Spring 2024), one of those projects focused on leveraging LLMs (Large Language Models) to streamline the creation of OpenTAP plugins in Python.
Penetration testing (a.k.a. "pen testing") plays a crucial role in identifying and mitigating security risks. It helps organizations strengthen defenses, protect sensitive data, and improve overall security posture. By leveraging test automation in general and OpenTAP in particular in penetration testing, organizations can improve the efficiency, accuracy, and effectiveness of their security testing efforts, helping them identify and remediate security vulnerabilities before they can be exploited by attackers.
Test automation, like the technology and products it targets, is in a state of constant change.
MarketsAndMarkets reports that the global test automation market size is expected to grow from USD 24.7 billion in 2022 to USD 52.7 billion by 2027, at a CAGR of 16.4%. To accompany the pace of the ever-changing testing landscape, you should be familiar with the latest test automation trends.
This second blog in our series on using OpenTAP for security testing, we take a deep dive into Vulnerability Assessment.
A software vulnerability describes a weakness or flaw in a software system that can be exploited by attackers to compromise the security of the system, its data, or its users. Vulnerabilities can exist in various components of software, including operating systems, drivers, applications, libraries, and firmware.
A source-available license grants users access to source code, allowing them to view, modify, and sometimes distribute the code. However, there may be restrictions or limitations imposed. These restrictions most often include limitations on commercial use, restrictions on redistributing modified versions, or requirements to share modifications with the original developer without necessarily making them public.
Dual Licensing (or multi-licensing) is the practice of releasing source code under multiple licenses. Most open source software is published and distributed under the rubric of a single license: Apache, GPL, Mozilla or about one hundred other licenses recognized by the Open Source Initiative.
Dual licensing, while adding complexity to use and management of open source software, serves several needs and application use cases:
