Symantecbeat
Welcome to Symantecbeat.
It consumes the REST API exposed by Symantec Endpoint Protection.See the docs https://apidocs.symantec.com/home/sep_15
Docker Image available at https://hub.docker.com/r/mariancraciunescu/symantecbeat
Ensure that this folder is at the following location:
${GOPATH}/src/github.com/marian-craciunescu/symantecbeat
Getting Started with Symantecbeat
Requirements
Init Project
To get running with Symantecbeat and also install the
dependencies, run the following command:
make setup
It will create a clean git history for each major step. Note that you can always rewrite the history if you wish before pushing your changes.
To push Symantecbeat in the git repository, run the following commands:
git remote set-url origin https://github.com/marian-craciunescu/symantecbeat
git push origin master
For further development, check out the beat developer guide.
Build
To build the binary for Symantecbeat run the command below. This will generate a binary
in the same directory with the name symantecbeat.
make
Run
To run Symantecbeat with debugging output enabled, run:
./symantecbeat -c symantecbeat.yml -e -d "*"
Test
To test Symantecbeat, run the following command:
make testsuite
alternatively:
make unit-tests
make system-tests
make integration-tests
make coverage-report
The test coverage is reported in the folder ./build/coverage/
Update
Each beat has a template for the mapping in elasticsearch and a documentation for the fields
which is automatically generated based on fields.yml
by running the following command.
make update
Cleanup
To clean Symantecbeat source code, run the following command:
make fmt
To clean up the build directory and generated artifacts, run:
make clean
Clone
To clone Symantecbeat from the git repository, run the following commands:
mkdir -p ${GOPATH}/src/github.com/marian-craciunescu/symantecbeat
git clone https://github.com/marian-craciunescu/symantecbeat ${GOPATH}/src/github.com/marian-craciunescu/symantecbeat
For further development, check out the beat developer guide.
Packaging
The beat frameworks provides tools to crosscompile and package your beat for different platforms. This requires docker and vendoring as described above. To build packages of your beat, run the following command:
make release
This will fetch and create all images required for the build process. The whole process to finish can take several minutes.