AI's new world challenges: What happened to security and privacy?
The rapid development of generative AI has created unprecedented challenges in privacy and security, triggering urgent calls for regulatory intervention.
Last week, I had the opportunity to discuss the security-related impacts of AI with some members of Congress and their staff in Washington, D.C.
Today’s generative AI reminds me of the Internet in the late 1980s, with basic research, latent potential, and academic uses, but it’s not yet ready for the public. This time, unchecked vendor ambition, fueled by minor league venture capital and inspired by Twitter echo chambers, is rapidly advancing AI’s “brave new world.”
The "public" base model is flawed and unsuitable for consumer and commercial use; privacy abstractions, if present, leak like a sieve; and security structures are important because attack surfaces and threat vectors are still being understood. As for the illusory guardrails, the less said the better.
So how did we get here? What happened to security and privacy?
Basic model of “compromise”
"Open" mode sometimes has limitations. Different vendors advertise their degree of openness through open mode weights, access to documentation or testing. Still, none of the major vendors provide anything close to the training dataset or its manifest or lineage information to be able to replicate and reproduce their models.
If you want to use one or more models to train a data set, then you as a consumer or organization do not have any ability to verify or confirm the extent of data contamination, whether with respect to intellectual property, copyright, etc., or as illegal content .
Crucially, without a manifest of the training data set, there is no way to verify or confirm non-existent malicious content. Malicious actors, including state-sponsored actors, plant Trojan content on the network that, if ingested during model training, results in unpredictable and potentially malicious side effects during inference.
Remember, once a model is compromised, there is no way to make it forget, the only option is to destroy it.
“Pervasive” security issues
Generative AI models are the ultimate safe honeypot because "all" data is ingested into a container. New categories of attack vectors have emerged in the AI era; the industry has yet to understand how these models are protected from cyber threats and the impact of how these models can be used as tools by cyber threat actors.
Malicious hint injection techniques may be used to pollute indexes; data poisoning may be used to corrupt weights; embedding attacks, including inversion techniques, may be used to extract rich data from embeddings; membership inference may be used to determine certain Whether the data is in the training set, etc., is just the tip of the iceberg.
Threat actors may gain access to confidential data through model inversion and programmatic querying; they may corrupt or otherwise influence the underlying behavior of the model; and, as mentioned earlier, large-scale uncontrolled data ingestion can result in Threats embedded in state-sponsored cyber activities, such as Trojan horses.
"Leaked" Privacy
AI models are only useful because of the data sets they are trained on; indiscriminate large-scale data ingestion creates unprecedented privacy risks for individuals and the public. In the AI era, privacy has become a social concern; regulations that primarily address personal data rights are insufficient.
In addition to static data, prompts for dynamic conversations must also be protected and maintained as intellectual property. If you are a consumer involved in co-creating an artifact with a model, you hope that the prompts you use to guide this creation activity will not be used to train the model or be shared with other model consumers.
If you are an employee using the model to achieve business outcomes, your employer expects your tips to be confidential; furthermore, tips and responses require a secure audit trail in case liability issues arise for either party. This is mainly due to the stochastic nature of these models and the changes in their responses over time.
What happens next?
We are dealing with an unprecedented technology that is unique in our computing history in that it exhibits emergent and latent behavior at scale; the methods used in the past for security, privacy, and confidentiality are no longer adequate.
Industry leaders threw caution to the wind, leaving regulators and policymakers with no choice but to step in.
The above is the detailed content of AI's new world challenges: What happened to security and privacy?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



In Debian systems, the readdir function is used to read directory contents, but the order in which it returns is not predefined. To sort files in a directory, you need to read all files first, and then sort them using the qsort function. The following code demonstrates how to sort directory files using readdir and qsort in Debian system: #include#include#include#include#include//Custom comparison function, used for qsortintcompare(constvoid*a,constvoid*b){returnstrcmp(*(

In Debian systems, readdir system calls are used to read directory contents. If its performance is not good, try the following optimization strategy: Simplify the number of directory files: Split large directories into multiple small directories as much as possible, reducing the number of items processed per readdir call. Enable directory content caching: build a cache mechanism, update the cache regularly or when directory content changes, and reduce frequent calls to readdir. Memory caches (such as Memcached or Redis) or local caches (such as files or databases) can be considered. Adopt efficient data structure: If you implement directory traversal by yourself, select more efficient data structures (such as hash tables instead of linear search) to store and access directory information

The readdir function in the Debian system is a system call used to read directory contents and is often used in C programming. This article will explain how to integrate readdir with other tools to enhance its functionality. Method 1: Combining C language program and pipeline First, write a C program to call the readdir function and output the result: #include#include#include#includeintmain(intargc,char*argv[]){DIR*dir;structdirent*entry;if(argc!=2){

Configuring a Debian mail server's firewall is an important step in ensuring server security. The following are several commonly used firewall configuration methods, including the use of iptables and firewalld. Use iptables to configure firewall to install iptables (if not already installed): sudoapt-getupdatesudoapt-getinstalliptablesView current iptables rules: sudoiptables-L configuration

This guide will guide you to learn how to use Syslog in Debian systems. Syslog is a key service in Linux systems for logging system and application log messages. It helps administrators monitor and analyze system activity to quickly identify and resolve problems. 1. Basic knowledge of Syslog The core functions of Syslog include: centrally collecting and managing log messages; supporting multiple log output formats and target locations (such as files or networks); providing real-time log viewing and filtering functions. 2. Install and configure Syslog (using Rsyslog) The Debian system uses Rsyslog by default. You can install it with the following command: sudoaptupdatesud

This article describes how to configure firewall rules using iptables or ufw in Debian systems and use Syslog to record firewall activities. Method 1: Use iptablesiptables is a powerful command line firewall tool in Debian system. View existing rules: Use the following command to view the current iptables rules: sudoiptables-L-n-v allows specific IP access: For example, allow IP address 192.168.1.100 to access port 80: sudoiptables-AINPUT-ptcp--dport80-s192.16

This article describes how to adjust the logging level of the ApacheWeb server in the Debian system. By modifying the configuration file, you can control the verbose level of log information recorded by Apache. Method 1: Modify the main configuration file to locate the configuration file: The configuration file of Apache2.x is usually located in the /etc/apache2/ directory. The file name may be apache2.conf or httpd.conf, depending on your installation method. Edit configuration file: Open configuration file with root permissions using a text editor (such as nano): sudonano/etc/apache2/apache2.conf

In Debian systems, OpenSSL is an important library for encryption, decryption and certificate management. To prevent a man-in-the-middle attack (MITM), the following measures can be taken: Use HTTPS: Ensure that all network requests use the HTTPS protocol instead of HTTP. HTTPS uses TLS (Transport Layer Security Protocol) to encrypt communication data to ensure that the data is not stolen or tampered during transmission. Verify server certificate: Manually verify the server certificate on the client to ensure it is trustworthy. The server can be manually verified through the delegate method of URLSession