Add security guidelines for locking down config, logPath and exportsPath

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • vNext
    • Affects Version/s: None
    • Component/s: None
    • None
    • Needed
    • Hide

      We need to highlight in:

      1. Our public facing documentation of MCP configuration
      2. Our security guidelines

      that logPath and exportsPath both should ideally be locked down and owned by the user running the MCP server with read/write permission to forbid any other process looking into these directories / files.

      Show
      We need to highlight in: Our public facing documentation of MCP configuration Our security guidelines that logPath and exportsPath both should ideally be locked down and owned by the user running the MCP server with read/write permission to forbid any other process looking into these directories / files.
    • Developer Tools

          Assignee:
          Himanshu Singh
          Reporter:
          Himanshu Singh
          Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

            Created:
            Updated:
            Resolved: