https://www.iis.net/learn/get-started/introduction-to-iis/introduction-to-iis-architecture#Hypertext
HTTP.sys
Hypertext Transfer Protocol Stack
HTTP.sys listens for HTTP requests from the network, passes the requests onto IIS for processing, and then returns processed responses to client browsers.
Kernel-mode caching
Requests for cached responses are served without switching to user mode.
Kernel-mode request queuing. Requests cause less overhead in context switching because the kernel forwards requests directly to the correct worker process. If no worker process is available to accept a request, the kernel-mode request queue holds the request until a worker process picks it up.
Request pre-processing and security filtering.
WWW
World Wide Web Publishing Service (WWW service) :
WWW Service is primarily responsible for configuring HTTP.sys, updating HTTP.sys when configuration changes, and notifying WAS
WAS
Windows Process Activation Service
manages application pool configuration and worker processes instead of the WWW Service
ISAPI:
internet server application programming interface
Worker process loads the aspnet_isapi.dll.
ISAPI filters can be registered with IIS to modify the behavior of a server.
filters can perform the following tasks:
Change request data (URLs or headers) sent by the client
Control which physical file gets mapped to the URL
Control the user name and password used with anonymous or basic authentication
Modify or analyze a request after authentication is complete
Modify a response going back to the client
Run custom processing on “access denied” responses
Run processing when a request is complete
Run processing when a connection with the client is closed
Perform special logging or traffic analysis.
Perform custom authentication.
Handle encryption and compression
w3wp
An Internet Information Services (IIS) worker process is a windows process (w3wp.exe) which runs Web applications, and is responsible for handling requests sent to a Web Server for a specific application pool.
It is the worker process for IIS. Each application pool creates at least one instance of w3wp.exe and that is what actually processes requests in your application.
It is not dangerous to attach to this, that is just a standard windows message.