SYS_PTRACE
Linux kernel capability must be added) or else RapidFort will not be able to trace the runtime behavior.docker images
and verify that the image is available:rflogin
to log into RapidFort. Enter your password if prompted.rfstub
to generate a stub image:docker.io/nginx:latest-rfstub
. The stub image contains dependencies necessary for RapidFort to trace the runtime behavior.docker images
to view the stub image:SYS_PTRACE
Linux kernel capability so that RapidFort is able to trace the runtime behavior:SYS_PTRACE
capability (--cap-add=SYS_PTRACE
) when running the stub image, then you may see the following error message:ptrace: Operation not permitted [/bin/dash]
ERROR 48e: did you forget to add SYS_PTRACE capability (--cap-add=SYS_PTRACE)?
docker.io/nginx:latest-rfstub
) is deployed and runningdocker run
command specified --cap-add=SYS_PTRACE
rfharden
to harden the stub image.docker.io/nginx:latest-rfhardened
.docker images
to view the hardened image:Error: No stub instances have run yet...
SYS_PTRACE
capability when running the hardened image.rfinfo <rapidfort_guid>
:rfinfo
with the -s
parameter.rfstub
to generate a stub image from the original image. The stub image contains dependencies necessary for RapidFort to trace the runtime behavior.SYS_PTRACE
Linux kernel capability by specifying --cap-add=SYS_PTRACE
so that RapidFort can trace the runtime behavior.rfharden
to generate a hardened image. The hardened image does not contain any RapidFort dependencies for runtime tracing.