Jamf

Scanner supports Jamf logs, which contain information related to device management, security, and user activities on Apple devices. In order for Scanner to see these logs, you can configure Jamf to publish them to S3.

Step 1: Configure Jamf to write logs to S3

You can use Jamf Log Stream to write logs to S3. You must reach out to Jamf support to enable this feature. You can follow the Jamf documentation set up S3 export. See: Jamf Premium Cloud Prerequisites.

Step 2: Link your S3 bucket to Scanner

If you haven't done so already, link the S3 bucket containing your Jamf logs to Scanner using the Linking AWS Accounts guide.

Step 3: Set up an S3 Import Rule in Scanner

1. Within Scanner, navigate to Settings > S3 Import Rules.

2. Click Create Rule.

3. For Rule name, type a name like my_team_name_jamf_logs.

4. For Destination Index, choose the index where you want these logs to be searchable in Scanner.

5. For Status, set to Active if you want to start indexing the data immediately.

6. For Source Type, we recommend jamf, but you are free to choose any name. However, out-of-the-box detection rules will expect jamf.

7. For AWS Account, choose the account that contains the S3 bucket containing Jamf logs.

8. For S3 Bucket, choose the S3 bucket containing Jamf logs.

9. For S3 Key Prefix, type the prefix (i.e. directory path) where the Jamf is writing logs.

10. For File type, choose JsonLines with Gzip compression.

11. For Timestamp extractors, under Column name, type timestamp. This is the field in each log event that contains the timestamp information.

12. Click Preview rule to try it out. Check that the S3 keys you expect are appearing, and check that the log events inside are being parsed properly with the timestamp detected properly.

13. When you're ready, click Create.