The only way to do it as described is to raise an an error if the log record isn't there, and the set up the job step with "Quit on failure". But this also means that the job will appear as failed, when the log record is missing. This is not going to be popular.
Better alternative is to have two jobs, for for checking the log file, and one for the SSIS package. Only the first job is scheduled. If the log record is there, this job step runs sp_start_job to start the other job.