Skip to content
Secure channel needed for historical deployment and shell-session audit
tailortrends
OP

3 hours ago

I am completing a security review of a Railway staging environment. Available deployment metadata attributes three historical deployments to my expected Railway account, but it does not identify the initiating client or authenticated session. Runtime logs also show four shell sessions without actor or command information.

Because this thread is public, I have intentionally omitted project, service, deployment, account, and session identifiers. What secure channel can a Hobby-plan customer use to provide those identifiers and request Railway’s retained audit attribution?

I need Railway to identify, to the extent retained:

  • The initiating client or source for each deployment
  • The actor and authentication method for each runtime shell
  • Non-secret session, token, connected-application, or SSH-key identifiers
  • Internal audit/event IDs
  • Source IP or device metadata, if retained

There is no active outage, and I am not requesting any deployment, configuration change, credential rotation, or production access. I can provide the exact resource IDs and UTC timestamps privately to an authorized Railway employee.

The AI assistant recommended contacting Railway because the exposed API metadata and runtime logs do not include the client- or session-level audit fields required to close the review.

Prepared with Railway's support template (v1).

Awaiting User Response

1 Reply

Railway
BOT

3 hours ago

Thanks for leaving the identifiers out of this public thread. You won't need to send them anywhere, because support doesn't provide audit attribution beyond what your workspace audit logs already show. That includes internal request or event IDs, client or session attribution for deployments, and a separate per-session forensic report.

For runtime shells, the audit log is the complete record of container access. SSHSession.authenticated and ContainerAccess.<action> events (shell, exec, files, tunnel) record the SSH key fingerprint, the target resource IDs, sourceIp, caller (dashboard, oauth, api, agent or system), grantedVia and the granted scope. We don't keep any command history or session transcript, and we don't record filenames or transfer contents.

On Hobby, the audit log shows the last 2 days of events. This viewing window isn't something support can extend or export past.


Status changed to Awaiting User Response Railway • about 3 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...